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 sbt
Recipients Jon.Oberheide, sbt
Date 2012-04-09.10:52:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333968762.94.0.141984861563.issue14532@psf.upfronthosting.co.za>
In-reply-to
Content
I only looked quickly at the web pages, so I may have misunderstood.

But it sounds like this applies when the attacker gets multiple chances to guess the digest for a *fixed* message (which was presumably chosen by the attacker).

That is not the case here because deliver_challenge() generates a new message each time.  Therefore the expected digest changes each time.
History
Date User Action Args
2012-04-09 10:52:42sbtsetrecipients: + sbt, Jon.Oberheide
2012-04-09 10:52:42sbtsetmessageid: <1333968762.94.0.141984861563.issue14532@psf.upfronthosting.co.za>
2012-04-09 10:52:42sbtlinkissue14532 messages
2012-04-09 10:52:42sbtcreate