Message 58603 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	gregory.p.smith
Recipients	donmez, gregory.p.smith, gvanrossum, loewis, theller
Date	2007-12-14.00:45:05
SpamBayes Score	0.030241244
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
"""code that has been audited and fixed in the past will again be vulnerable.""" That code wasn't properly audited or fixed if it depended on integer overflow behavior. Anyways, I'm glad we have the flag to disable the optimization on gcc in the meantime. We should open a bug regarding fixing all of pythons integer overflows. gcc is only one compiler. Other compilers are free to behave in exactly the same manner. I've opened http://bugs.python.org/issue1621 to track the larger code fix.

"""code that has been audited and fixed in the past will again be
vulnerable."""

That code wasn't properly audited or fixed if it depended on integer
overflow behavior.

Anyways, I'm glad we have the flag to disable the optimization on gcc in
the meantime.

We should open a bug regarding fixing all of pythons integer overflows.
 gcc is only one compiler.  Other compilers are free to behave in
exactly the same manner.

I've opened http://bugs.python.org/issue1621 to track the larger code fix.

History
Date	User	Action	Args
2007-12-14 00:45:05	gregory.p.smith	set	spambayes_score: 0.0302412 -> 0.030241244 recipients: + gregory.p.smith, gvanrossum, loewis, theller, donmez
2007-12-14 00:45:05	gregory.p.smith	set	spambayes_score: 0.0302412 -> 0.0302412 messageid: <[email protected]>
2007-12-14 00:45:05	gregory.p.smith	link	issue1608 messages
2007-12-14 00:45:05	gregory.p.smith	create