[Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited)
Serhiy Storchaka
storchaka at gmail.com
Sun Apr 10 17:07:48 EDT 2016
More information about the Python-Dev mailing list
Sun Apr 10 17:07:48 EDT 2016
- Previous message (by thread): [Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited)
- Next message (by thread): [Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10.04.16 19:51, Jon Ribbens wrote: > On Sun, Apr 10, 2016 at 02:51:23PM +1000, Nick Coghlan wrote: >> On 9 April 2016 at 22:43, Victor Stinner <victor.stinner at gmail.com> wrote: >>> See pysandbox test suite for a lot of ways to escape a sandbox. CPython has >>> a list of know code to crash CPython (I don't recall the dieectory in >>> sources), even with the latest version of CPython. >> >> They're at https://hg.python.org/cpython/file/tip/Lib/test/crashers > > Thanks. I take your point that sandboxing Python requires CPython to > free of code execution bugs. However I will note that none of the > crashers in that directory will work inside my experiment (except > "infinite_loop_re.py", which isn't a crasher just a long loop). Try following example: it = iter([1]) for i in range(1000000): it = filter(None, it) next(it)
- Previous message (by thread): [Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited)
- Next message (by thread): [Python-Dev] Challenge: Please break this! (a.k.a restricted mode revisited)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list