[issue13703] Hash collision security issue
Gregory P. Smith
report at bugs.python.org
Sun Feb 12 02:37:26 CET 2012
Gregory P. Smith <greg at krypto.org> added the comment:
Should -R be required to take a parameter specifying "on" or "off" so
that code using a #! line continues to work as specified across the a
change in default behavior when upgrading from 3.2 to 3.3?
#!/usr/bin/python3 -R on
#!/usr/bin/python3 -R off
In 3.3 it would be a good idea to have a command line flag to turn
this off. Rather than introducing a new flag in 3.3 a parameter that
is specific without regards for the default avoids that entirely.
before anyone suggests it: I do *not* think -R should accept a value
to use as the seed. that is unnecessary.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list