From 73a229c3a5032d50f21de698869cf2117084d12f Mon Sep 17 00:00:00 2001 From: shugo Date: Fri, 14 Jun 2013 00:53:37 +0000 Subject: * NEWS: add notes for $SAFE. * doc/security.rd: remove the description of $SAFE=4. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41290 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- doc/security.rdoc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'doc/security.rdoc') diff --git a/doc/security.rdoc b/doc/security.rdoc index 2cf6531785..d552f9876c 100644 --- a/doc/security.rdoc +++ b/doc/security.rdoc @@ -21,12 +21,7 @@ Ruby provides a mechanism to restrict what operations can be performed by Ruby code in the form of the $SAFE variable. However, $SAFE does not provide a secure environment for executing -untrusted code even at its maximum level of +4+. $SAFE is -inherently flawed as a security mechanism, as it relies on every unsafe -operation performed by any C method to be guarded by a $SAFE -check. If this check is ever missed, the entire security of the system is -compromised. $SAFE also does not offer any protection against -denial of service attacks. +untrusted code. If you need to execute untrusted code, you should use an operating system level sandboxing mechanism. On Linux, ptrace or LXC can be used to sandbox -- cgit v1.2.3