From: matz@... (Yukihiro Matsumoto)
Date: 2000-03-17T01:04:14+09:00
Subject: [ruby-talk:01899] Re: [ruby-1.5.3] require / SAFE


In message "[ruby-talk:01889] [ruby-1.5.3] require / SAFE"
    on 00/03/16, ts <decoux@moulon.inra.fr> writes:

| I don't understand this modification and its consequence :
|
|        * eval.c (rb_f_require): prohibiting require() in the secure mode
|          cause serious autoloading error.
|
| If require is authorized ruby will try, next, to modify rb_features and this
| will give a security error, no ?

It used to raise SecurityError in $SAFE >= 4, but changed not to raise
exception then.

| What are the implications for a script running with $SAFE > 4 ?

 $SAFE = 0 no check
 $SAFE = 1 check dangerous operation by tainted string.
 $SAFE = 2 several process checks added
 $SAFE = 3 all strings be tainted; untrusted script
 $SAFE = 4 allow coexistence of trusted/untrusted code (e.g. applet)
 $SAFE > 4 undefined (yet)

							matz.