4 ms·

Wonder why didn't they add GCM with ECDHE even though it is already in Win10 preview. I considered it strange that they added GCM with DHE in the first place wh

by yuhong 12y ago

Wonder why didn't they add GCM with ECDHE even though it is already in Win10 preview. I considered it strange that they added GCM with DHE in the first place when all the rest of the suites are ECDHE.

mike_hearn 12y ago
From the article: Does this update contain any additional security-related changes to functionality? Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes changes to available TLS cipher suites. This update includes new TLS cipher suites that offer more robust encryption to protect customer information. These new cipher suites all operate in Galois/counter mode (GCM), and two of them offer perfect forward secrecy (PFS) by using DHE key exchange together with RSA authentication.
- Perseids 12y ago
  I don't see the relevance of the quote. It only states the changes and not why other changes were not made.
higherpurpose 12y ago
Too bad they didn't add support for ChaCha20 and Poly1305 https://www.imperialviolet.org/2013/10/07/chacha20.html https://www.imperialviolet.org/2013/10/07/chacha20.html Also, did they even add support for Curve25519? Or are they still forcing us all to trust the (almost certainly) tainted NIST curves?
- Strom 12y ago
  While ChaCha20/Poly1305/Curve25519 are nice, they aren't part of standard TLS, and even OpenSSL doesn't support them.
m0dest 12y ago
Agree, this is super strange. No one wants to use DHE because of the performance impact. Windows 7 and later do already support ECDHE + GCM, but only when combined with ECDSA. In practice, nobody can use ECDSA because old clients still need RSA certificates. So we continue to wait for TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, which is clearly the cipher suite that everyone wants. Years later, still not available for Windows Server.

4 ms·

Wonder why didn't they add GCM with ECDHE even though it is already in Win10 preview. I considered it strange that they added GCM with DHE in the first place wh

by yuhong 12y ago

mike_hearn 12y ago
From the article: Does this update contain any additional security-related changes to functionality? Yes. In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes changes to available TLS cipher suites. This update includes new TLS cipher suites that offer more robust encryption to protect customer information. These new cipher suites all operate in Galois/counter mode (GCM), and two of them offer perfect forward secrecy (PFS) by using DHE key exchange together with RSA authentication.
- Perseids 12y ago
  I don't see the relevance of the quote. It only states the changes and not why other changes were not made.
higherpurpose 12y ago
Too bad they didn't add support for ChaCha20 and Poly1305 https://www.imperialviolet.org/2013/10/07/chacha20.html https://www.imperialviolet.org/2013/10/07/chacha20.html Also, did they even add support for Curve25519? Or are they still forcing us all to trust the (almost certainly) tainted NIST curves?
- Strom 12y ago
  While ChaCha20/Poly1305/Curve25519 are nice, they aren't part of standard TLS, and even OpenSSL doesn't support them.
m0dest 12y ago
Agree, this is super strange. No one wants to use DHE because of the performance impact. Windows 7 and later do already support ECDHE + GCM, but only when combined with ECDSA. In practice, nobody can use ECDSA because old clients still need RSA certificates. So we continue to wait for TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, which is clearly the cipher suite that everyone wants. Years later, still not available for Windows Server.