[Python-Dev] For sandboxing: alternative to crippling file()
Armin Rigo
arigo at tunes.org
Fri Jun 30 19:52:05 CEST 2006
More information about the Python-Dev mailing list
Fri Jun 30 19:52:05 CEST 2006
- Previous message: [Python-Dev] For sandboxing: alternative to crippling file()
- Next message: [Python-Dev] For sandboxing: alternative to crippling file()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Brett,
On Thu, Jun 29, 2006 at 11:48:36AM -0700, Brett Cannon wrote:
> 1) Is removing 'file' from the builtins dict in PyInterpreterState (and
> maybe some other things) going to be safe enough to sufficiently hide 'file'
> confidently (short of someone being stupid in their C extension module and
> exposing 'file' directly)?
No.
>>> object.__subclasses__()
[..., <type 'file'>]
Maybe this one won't work if __subclasses__ is forbidden, but in general
I think there *will* be a way to find this object.
A bientot,
Armin
- Previous message: [Python-Dev] For sandboxing: alternative to crippling file()
- Next message: [Python-Dev] For sandboxing: alternative to crippling file()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list