Simple Python question for some
rosuav at gmail.com
Mon Oct 29 06:03:47 CET 2012
On Mon, Oct 29, 2012 at 3:30 PM, Evan Driscoll <driscoll at cs.wisc.edu> wrote:
> On 10/28/2012 7:18 PM, Chris Angelico wrote:
>> Which means that strings will ALWAYS be compared as strings, and
>> numbers will ALWAYS be compared as numbers, and ne'er the twain shall
>> conflict. I can trust Python to compare MD5 hashes reliably:
>>>>> "912128034267498495410681495015e0" !=00912128034267498495410681495015"
>> Of course, I'm not pointing fingers at any other languages here, but
>> this is a known security hole in one rather widely-used one.
> If you are PerHaPs talking about the language I think you are, my
> favorite fact about that is I'm that I think a while back I saw a bug
> entry about something like that and they weren't sure how or even if it
> should be fixed.
Indeed. So it's an issue unlikely to go away any time soon.
More information about the Python-list