Reviving restricted mode?
[Posted March 4, 2009 by jake]
| From: |
| Guido van Rossum <guido-AT-python.org> |
| To: |
| Python-Dev <python-dev-AT-python.org> |
| Subject: |
| Reviving restricted mode? |
| Date: |
| Sun, 22 Feb 2009 08:45:27 -0800 |
| Message-ID: |
| <ca471dc20902220845g187dae52nd3b3779b3cacfe4d@mail.gmail.com> |
| Archive-link: |
| Article, Thread
|
I've received some enthusiastic emails from someone who wants to
revive restricted mode. He started out with a bunch of patches to the
CPython runtime using ctypes, which he attached to an App Engine bug:
http://code.google.com/p/googleappengine/issues/detail?id...
Based on his code (the file secure.py is all you need, included in
secure.tar.gz) it seems he believes the only security leaks are
__subclasses__, gi_frame and gi_code. (I have since convinced him that
if we add "restricted" guards to these attributes, he doesn't need the
functions added to sys.)
I don't recall the exploits that Samuele once posted that caused the
death of rexec.py -- does anyone recall, or have a pointer to the
threads?
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-...
(
Log in to post comments)