From: Yukihiro Matsumoto <matz@...>
Date: 2009-10-07T12:48:47+09:00
Subject: [ruby-core:25982] Re: Disabling tainting

Hi,

In message "Re: [ruby-core:25981] Re: Disabling tainting"
    on Wed, 7 Oct 2009 12:11:57 +0900, Tony Arcieri <tony@medioh.com> writes:

|To really build a secure system around something like $SAFE/taint, you must
|be extremely vigilant with handling the flow of tainted objects through the
|system.  One little mistake anywhere and it doesn't offer you any security
|at all.

As an application security should be perfect.  But in the process of
developing one, detecting even 50% of security issues are using, and I
believe taint system catches far more than 50%.

|> It might not be useful for you but some ruby programs developed on
|> early era often use it.
|
|That's fine, but 99.9% of Ruby programs out there don't use it and it
|impacts performance, so isn't making it an on-by-default configurable option
|a good idea?

Did you say "impacts"?  Do you know how much impact it does for
performance?  I don't buy any performance proposals without
measurement.  I am afraid you cannot measure any difference at all,
when you remove tainting.

							matz.