[issue8680] Add a sandbox in Distutils2

Changes by Éric Araujo : -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue8680] Add a sandbox in Distutils2

Éric Araujo added the comment: I think there is some py3 support in pysandbox, but I’m not sure, and this discussion is off-topic for this bug tracker. If you don’t find anything in the links on the pysandbox page, feel free to ask on the python-list mailing list. -- __

[issue8680] Add a sandbox in Distutils2

th3flyboy added the comment: Cool, thanks for that link, that should really help. One quick question however, do you or anyone else know if that will work under Python 3, we currently use 2, however it would be nice to be able to future proof for moving to 3. --

[issue8680] Add a sandbox in Distutils2

Éric Araujo added the comment: We’re saying the same thing :) It all depends on the promise: If you’re making a best-effort sandbox, you’re trying to do the best you can, in cooperation with your users. For a game, I think you want an iron-clad sandbox that is totally error-proof. See http

[issue8680] Add a sandbox in Distutils2

th3flyboy added the comment: Hey, even if it's not perfect, it would be nice to at least see partial sand boxing in Python, rather than none at all. I'm working on an open source game project that uses Python, but recently the issue of security came up involving using python scripts with mali

[issue8680] Add a sandbox in Distutils2

Changes by Éric Araujo : -- versions: +3rd party -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___ ___

[issue8680] Add a sandbox in Distutils2

Éric Araujo added the comment: I talked a bit about that with haypo. A strong sandbox would have to intercept a number of C and Python calls to catch everything. The sandbox module in setuptools/distribute does that in 250 lines. I’m not sure it catches C code run from extension modules being

[issue8680] Add a sandbox in Distutils2

Éric Araujo added the comment: What kind of sandbox should that be? Best-effort, meaning it replaces some functions to provide the dry-run feature, or an iron-clad sandbox that blocks malicious code from breaking out? -- nosy: +merwok versions: +Python 2.5, Python 2.6, Python 2.7, Pyt

[issue8680] Add a sandbox in Distutils2

Changes by Dan Buch : -- nosy: +meatballhat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8680] Add a sandbox in Distutils2

New submission from Tarek Ziadé : Add a sandbox in distutils2, so all installation steps can be recorded or controlled. Usage example: a dry-run mode that prevents anything to be written on the disk but just reports. See setuptools.sandbox for example -- assignee: tarek components: D