[TLS] Issue 49: Finished.verify length

To: tls at ietf.org
Subject: [TLS] Issue 49: Finished.verify length
From: Eric Rescorla <ekr at networkresonance.com>
Date: Thu, 13 Sep 2007 11:34:53 -0700
Cc:
List-archive: <http://www1.ietf.org/pipermail/tls>
List-help: <mailto:tls-request@lists.ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-post: <mailto:tls@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
User-agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)

Pasi asks:

  Currently Finished.verify_data is always 12 octets. With newer PRFs
  and hashes, more might be useful. Should this depend on the PRF?
  
My take on this is that the 12-octet length is mostly independent
of the PRF. After all, it's already been truncated from either 
MD5 or SHA-1. Is there a good security reason to change this?

-Ekr

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

Follow-Ups:
- Re: [TLS] Issue 49: Finished.verify length
  - From: Mike

Prev by Date: Re: [TLS] Issue 56: AES as MTI
Next by Date: Re: [TLS] Issue 49: Finished.verify length
Previous by thread: [TLS] Issue 56: AES as MTI
Next by thread: Re: [TLS] Issue 49: Finished.verify length
Index(es):
- Date
- Thread

[TLS] Issue 49: Finished.verify length

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