[Python-Dev] doc for new restricted execution design for Python (original) (raw)
Brett Cannon brett at python.org
Tue Jun 27 20:06:30 CEST 2006
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/27/06, Scott David Daniels <Scott.Daniels at acm.org> wrote:
Brett Cannon wrote: > On 6/27/06, Jim Jewett <jimjjewett at gmail.com> wrote: >> ... >> Caps and current usage should also be available (though read-only) >> from python; it is quite sensible to spill some cache when getting too >> close to your memory limit. > > Yeah, being able to read your restrictions seems reasonable to do from an > untrusted interpreter. Certainly in some cases I'd like to run a Python program that claims it "plays nice" without its being able to see that it is in jail. Otherwise I can't escalate my trust of the code based on old behavior (it might be nice only when the jailer is around). So, reading your restrictions is a capability I'd like to be able to control.
Sounds reasonable.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060627/2e0316f6/attachment.html
- Previous message: [Python-Dev] doc for new restricted execution design for Python
- Next message: [Python-Dev] doc for new restricted execution design for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]