[ruby-talk:00972] Re: Bastion or SecurityManager for Ruby?

Hi,

Yukihiro Matsumoto writes:
> Hi,
> 
> In message "[ruby-talk:00964] Bastion or SecurityManager for Ruby?"
>     on 99/12/10, Clemens Hintze <[e-mail]> writes:
> 

[...]

> 
> How about removing them explicitly by rb_remove_method().
> 
>   void rb_remove_method(VALUE klass, const char *name);
> 
> The socket interface is implemented by extension, so that prohibiting
> require restricts them.

I was aware of this. But I don't like that way too much. I fear to
oversee anything important, you know?

> 
> The other possibility is using `safe level', by setting it level 3
> using `rb_set_safe_level(3)', the untrusted script should run safely.
> open, system, require, etc. will cause SecurityError exception.
> Notice `safe level' feature may not be complete, it's still under
> development. 

That is the same hint, nakajima kengo has told me with the -T switch,
isn't it?

> 
> Hope this helps.

Yep!

> 
> 							matz.

\cle