Re: [TLS] Issue 49: Finished.verify length
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TLS] Issue 49: Finished.verify length



As I recall, the truncation was intended to *increase* security,
because it leaked less information about the MS to an active
attacker.

Well, the Finished message follows ChangeCipherSpec, so it is encrypted when the attacker receives it. I was thinking about the other direction where the attacker convinces you (via his Finished message) that a session has been established, making you think it's ok to send your sensitive information, which he can then work offline to try to decode. His Finished message would also have to be correctly encrypted and MAC'ed, so I imagine it would be extremely difficult to forge in any case....

Mike

_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.