summaryrefslogtreecommitdiffstats
path: root/Lib/test/crashers/bogus_code_obj.py
diff options
context:
space:
mode:
Diffstat (limited to 'Lib/test/crashers/bogus_code_obj.py')
-rw-r--r--Lib/test/crashers/bogus_code_obj.py10
1 files changed, 10 insertions, 0 deletions
diff --git a/Lib/test/crashers/bogus_code_obj.py b/Lib/test/crashers/bogus_code_obj.py
index 5438d91..613ae51 100644
--- a/Lib/test/crashers/bogus_code_obj.py
+++ b/Lib/test/crashers/bogus_code_obj.py
@@ -1,5 +1,15 @@
"""
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