Re: [TLS] Updated TLS 1.2 I-D

7.4.3. Server key exchange message

<snip>

   If the SignatureAlgorithm being used to sign the ServerKeyExchange
   message is DSA, the hash function used MUST be SHA-1. If the
   SignatureAlgorithm it must be the same hash function used in the
   signature of the server's certificate (found in the Certificate)
   message. This algorithm is denoted Hash below. Hash.length is the
   length of the output of that algorithm.

Something is missing in this sentence  "If the SignatureAlgorithm it must 
be the " 

-----------------------------------------------
Robert Dugal
Member of Development Group
Certicom Corp.
EMAIL: rdugal@certicom.com
PHONE: (905) 501-3848
FAX  : (905) 507-4230
WEBSITE: www.certicom.com

Eric Rescorla <ekr@networkresonance.com> wrote on 06/25/2006 12:54:30 PM:

> I've submitted an update TLS 1.2 I-D an in the meantime
> you can find it at:
> 
> http://scm.sipfoundry.org/rep/ietf-drafts/ekr/tls/tls.txt
> 
> The big thing I know is misisng is replaceable PRFs, which
> I wanted to discuss on the mailing list before I put in.
> As people will recall, there was a consensus on replaceable
> PRFs/KDFs in Dallas but we didn't discuss exactly how to do
> them.
> 
> My proposal is as follows:
> 
> - All PRFs must have the same "API" as the existing TLS 
>   PRFs.
> - New cipher suites MAY have as part of their specification
>   a new PRF.
> - There is no way to separately negotiate a new PRF for
>   an existing cipher suite.
> 
> The major alternative is some kind of extension, which makes
> me uncomfortable. 
> 
> Thoughts? Issues?
> -Ekr
> 
> 
> 
> 
> _______________________________________________
> TLS mailing list
> TLS@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/tls