As the ts said, setting the $SAFE is a way to ignore the warning.
Or
run the ruby script like this:
ruby -w0 file...

Last we can change the permission of the dictionary.
For example,
drwxr-xr-x  7 abc abc ...... /home/abc/bin
Let other users can only access the dictionary.


ts wrote:
>>>>>> "S" == Sean Harre <sharre / transmeta.com> writes:
> 
> S> substitutions/matching, etc. That makes sense. But is there an 
> "official
> S> workaround" for this problem? And if not, can I rest well at night 
> with
> 
>  Yes, correct the problem (i.e. change the permission for the directory)
>  :-)
> 
> S> my '\n' workaround in my companys stable source tree? It's just a
> S> warning message now, but in the future, I can't really forsee any
> 
>  it's a warning message with $SAFE = 0, but an error with $SAFE >= 1
> 
> svg% ruby -e 'exec("ls")'
> -e:1: warning: Insecure world writable dir /home/ts/XXX/., mode 040777
> svg%
> 
> svg% ruby -e '$SAFE = 1; exec("ls")'
> -e:1: warning: Insecure world writable dir /home/ts/XXX/., mode 040777
> -e:1:in `exec': Insecure PATH - ls (SecurityError)
>   from -e:1
> svg%
> 
> 
> Guy Decoux

-- 
Posted via http://www.ruby-forum.com/.