RE: [TLS] TLS 1.2 hash agility

[<Pasi.Eronen at nokia.com>]

mike-list at pobox.com wrote:

> > - In the case of the ServerKeyExchange, the client signals his
> >   support in this extension *and* in the cipher suite.
> 
> The cipher suite doesn't have all the information about which
> signature algorithm to use.
> 
>      TLS_RSA_WITH_RC4_128_MD5
>      TLS_RSA_WITH_RC4_128_SHA
>      TLS_RSA_WITH_3DES_EDE_CBC_SHA
>      TLS_RSA_WITH_AES_128_CBC_SHA
>      TLS_RSA_WITH_AES_256_CBC_SHA
> 
> The above cipher suites specify that the public key in the
> certificate must be an RSA key, but they don't say anything about
> what algorithm is used to sign the certificate.

In TLS 1.0 and 1.1, these ciphersuites required that the certificate
is also signed with RSA. (But that's something we can change in 
TLS 1.2, if we so decide.)

Best regards,
Pasi

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