Paul Rubin <http://[EMAIL PROTECTED]> writes: > Mike Meyer <[EMAIL PROTECTED]> writes: >> >> Compile-time restrictions don't matter for squat - you need >> >> serious restrictions on what the program can do at runtime. >> > You need both. >> Yup. Any language besides Java even *try* to provide both for a >> production environment? > Yes. Python tried. It had a module called rexec for that purpose. > I keep mentioning that, and you keep ignoring it. Rexec was around > for a long time, and was removed for technical reasons with some > reluctance. There is nothing un-Pythonic about the idea.
If you've mentioned it before, it wasn't to me. Or maybe my news server dropped it. Rexec was removed because it didn't work. Just like bastion and every other attempt to create a "safe" environment in Python. Any security wonk worth his pay will tell you that you don't add security to something after the fact if you want good security. You design it in from the beginning. Of course, what rexec tried to do and what "private" do are orthogonal issues. <mike -- Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. -- http://mail.python.org/mailman/listinfo/python-list