[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18336] The new concept of 'trust'

From: Dave Thomas <dave@...>
Date: 2008-08-19 13:52:30 UTC
List: ruby-core #18336
I've been looking through the new concept of 'trust' in Ruby 1.9, and  
I'd like to make sure I'm understanding the motivation behind it and  
the way it should be used.

It seems to parallel the concept of 'taintedness.' But whereas  
taintedness is intended to keep track of incoming data, trust seems to  
keep track of internal execution. That is, once the safe level has  
been set to 3, all objects that are subsequently created are by  
default untrusted.

I'm not clear, however, how this can be used in practice. Is it  
intended to be used in code sandboxes?


Dave

In This Thread

Prev Next