[sake] sake -e Rakefile fails

#49

$ sake -e Rakefile
/opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/lib/sake.rb:312:in `parse': /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': Insecure operation - gem_original_require (SecurityError)
        from /opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/lib/sake.rb:312:in `join'
        from /opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/lib/sake.rb:312:in `parse'
        from /opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/lib/sake.rb:241:in `examine'
        from /opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/lib/sake.rb:131:in `run'
        from /opt/local/lib/ruby/gems/1.8/gems/sake-1.0.6/bin/sake:5
        from /opt/local/bin/sake:16:in `load'
        from /opt/local/bin/sake:16

Reported by Dr Nic · June 27th, 2007 @ 04:15 PM

Activity

Chris Wanstrath
- State changed from new to hold
It's because $SAFE is set to 3.
Maybe it should only be 3 when doing an open() over the net?
I didn't want an `rm -rf` in the Rakefile to screw you. If you run a task and it's in there, your fault (that's why -e exists), but it seems unfair to assume we can safely eval() any Rakefile that exists.

June 27th, 2007 @ 04:15 PM
Harry Vangberg
- Tag set to sake
It might be me, but how do I change this?

I tried setting $SAFE = 0 and ENV['SAFE'] = 0. Didn't work.

August 25th, 2008 @ 03:28 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.