dertown wrote:
Is there a place where we can start getting some requiremnts together for a
new Ruby Security implentation. Then it would be possible to completely
replace SAFE and Taint.
Would people want to use the same api if possible?
Well right here on the list would be a great start. And of course
starting a Wiki page we can all update would help make it more publicly
readable. It would also give us something to pint ko1, matz, and others
at for discussions about API and semantics.
There's two bottom lines I can think of, since I'm not well-versed in
the actual security stuff:
- it must be something that can be implemented in MRI/KRI, possibly
using the same API/mechanisms used right now.
- it must not introduce overhead back into the system like taint/safe
does now.
There's a start...how about some actual requirements on the wiki?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
