Linux vps-61133.fhnet.fr 4.9.0-19-amd64 #1 SMP Debian 4.9.320-2 (2022-06-30) x86_64
Apache/2.4.25 (Debian)
Server IP : 93.113.207.21 & Your IP : 216.73.216.119
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
src /
Python-3.10.14 /
Lib /
test /
crashers /
Delete
Unzip
Name
Size
Permission
Date
Action
README
1
KB
-rw-r--r--
2024-03-19 22:46
bogus_code_obj.py
628
B
-rw-r--r--
2024-03-19 22:46
gc_inspection.py
1.07
KB
-rw-r--r--
2024-03-19 22:46
infinite_loop_re.py
645
B
-rw-r--r--
2024-03-19 22:46
mutation_inside_cyclegc.py
753
B
-rw-r--r--
2024-03-19 22:46
recursive_call.py
358
B
-rwxr-xr-x
2024-03-19 22:46
trace_at_recursion_limit.py
376
B
-rw-r--r--
2024-03-19 22:46
underlying_dict.py
282
B
-rw-r--r--
2024-03-19 22:46
Save
Rename
""" Broken bytecode objects can easily crash the interpreter. This is not going to be fixed. It is generally agreed that there is no point in writing a bytecode verifier and putting it in CPython just for this. Moreover, a verifier is bound to accept only a subset of all safe bytecodes, so it could lead to unnecessary breakage. For security purposes, "restricted" interpreters are not going to let the user build or load random bytecodes anyway. Otherwise, this is a "won't fix" case. """ import types co = types.CodeType(0, 0, 0, 0, 0, 0, b'\x04\x00\x71\x00', (), (), (), '', '', 1, b'') exec(co)