[Python-Dev] doc for new restricted execution design for Python (original) (raw)

Brett Cannon brett at python.org
Wed Jun 28 18:57:48 CEST 2006

On 6/28/06, Guido van Rossum <guido at python.org> wrote:

On 6/28/06, Jim Jewett <jimjjewett at gmail.com> wrote: > On 6/27/06, Neal Norwitz <nnorwitz at gmail.com> wrote: > > On 6/27/06, Brett Cannon <brett at python.org> wrote: > > > > > > > (5) I think file creation/writing should be capped rather than > > > > binary; it is reasonable to say "You can create a single temp file up > > > > to 4K" or "You can create files, but not more than 20Meg total". > > > > That has been suggested before. Anyone else like this idea? > > > [ What exactly does the limit mean? bytes written? bytes currently stored? bytes stored after exit?] > > IMHO, I would prefer that it limit disk consumption; a deleted or > overwritten file would not count against the process, but even a > temporary spike would need to be less than the cap. Some additional notes: - File size should be rounded up to some block size (512 if you don't have filesystem specific information) before adding to the total.

Why?

If you want that kind of cap, just specify individual files you are willing to let people open for reading; that is your cap. Only have to worry about this if you open an entire directory open for writing.

Once again, another one of those balance issues of where do we draw the line in terms of simplicity in the setting compared to controlling every possible setting people will want (especially, it seems, when it comes to writing to disk). And if you want to allow directory writing, you need to allow use of the platform's OS-specific module (e.g., posix) to do it since open() won't let you create a directory.

I really want to keep the settings and setup simple. I don't want to overburden people with a ton of security settings.

(I find reading about trusted and untrusted code confusing; a few

times I've had to read a sentence three times before realizing I had swapped those two words. Perhaps we can distinguish between trusted and sandboxed? Or even native and sandboxed?)

Fair enough. When I do the next draft I will make them more distinctive (probably "trusted" and "sandboxed").

-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060628/42d76a73/attachment.htm

More information about the Python-Dev mailing list