ietf
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC

2010-12-08 17:34:03
from [Francis Dupont] [Permanent Link] 
 In your previous mail you wrote:

   The logic doesn't make sense in this position.  "Crypto modules
   can't use MD5, thus no protocols at all should use MD5."
   
=> this is a silly/bad/... consequence of the crypto label
attached to the MD5 name. I understand you are not happy with
this but what do you propose?

Regards

Francis(_dot_)Dupont(_at_)fdupont(_dot_)fr

PS: BTW I'd like to apply the argument only to *new* protocols.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [certid] Second Last Call: draft-saintandre-tls-server-id-check (...) to BCP, Peter Saint-Andre
Next by Date:  RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
Previous by Thread:  RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Christian Huitema
Next by Thread:  RE: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms) to Informational RFC, Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
Indexes:  [Date] [Thread] [Top] [All Lists]