變更 Windows 10 與 Windows Server 2016 TLS (Schannel SSP)TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016

適用於:Windows Server 2016 和 Windows 10Applies To: Windows Server 2016 and Windows 10

密碼套件變更Cipher Suite Changes

Windows 10,版本 1511 年與 Windows Server 2016 新增密碼套件訂單使用行動裝置管理 (MDM) 設定支援。Windows 10, version 1511 and Windows Server 2016 add support for configuration of cipher suite order using Mobile Device Management (MDM).

套件優先順序訂單變更密碼,請查看密碼套件 Schannel 在For cipher suite priority order changes, see Cipher Suites in Schannel.

新增的支援下列加密套件:Added support for the following cipher suites:

  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (RFC 5289) Windows 10、1507 版和 Windows Server 2016 中TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (RFC 5289) in Windows 10, version 1507 and Windows Server 2016
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (RFC 5289) Windows 10、1507 版和 Windows Server 2016 中TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (RFC 5289) in Windows 10, version 1507 and Windows Server 2016

變更下列加密套件 DisabledByDefault:DisabledByDefault change for the following cipher suites:

  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (RFC 5246) 在 Windows 10,版本 1703 年TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (RFC 5246) in Windows 10, version 1703
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (RFC 5246) 在 Windows 10,版本 1703 年TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (RFC 5246) in Windows 10, version 1703
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA (RFC 5246) 在 Windows 10,版本 1703 年TLS_DHE_DSS_WITH_AES_256_CBC_SHA (RFC 5246) in Windows 10, version 1703
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA (RFC 5246) 在 Windows 10,版本 1703 年TLS_DHE_DSS_WITH_AES_128_CBC_SHA (RFC 5246) in Windows 10, version 1703
  • TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (RFC 5246) 在 Windows 10,版本 1703 年TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (RFC 5246) in Windows 10, version 1703
  • 在 Windows 10,版本 1709 TLS_RSA_WITH_RC4_128_SHATLS_RSA_WITH_RC4_128_SHA in Windows 10, version 1709
  • 在 Windows 10,版本 1709 TLS_RSA_WITH_RC4_128_MD5TLS_RSA_WITH_RC4_128_MD5 in Windows 10, version 1709

開始使用 Windows 10、1507 版和 Windows Server 2016、預設不支援 SHA 512 憑證。Starting with Windows 10, version 1507 and Windows Server 2016, SHA 512 certificates are supported by default.

RSA 變更RSA key changes

Windows 10、1507 版和 Windows Server 2016 新增 client RSA 金鑰大小登錄設定選項。Windows 10, version 1507 and Windows Server 2016 add registry configuration options for client RSA key sizes.

如需詳細資訊,請查看KeyExchangeAlgorithm-Client RSA 金鑰大小For more information, see KeyExchangeAlgorithm - Client RSA key sizes.

時間時變更Diffie-Hellman key changes

Windows 10、1507 版和 Windows Server 2016 新增時間時金鑰大小登錄設定選項。Windows 10, version 1507 and Windows Server 2016 add registry configuration options for Diffie-Hellman key sizes.

如需詳細資訊,請查看KeyExchangeAlgorithm-時間時金鑰大小For more information, see KeyExchangeAlgorithm - Diffie-Hellman key sizes.

SCH_USE_STRONG_CRYPTO 選項變更SCH_USE_STRONG_CRYPTO option changes

Windows 10、1507 版與 Windows Server 2016 SCH_USE_STRONG_CRYPTO選項現在停用 NULL,MD5,DES,及匯出加密。With Windows 10, version 1507 and Windows Server 2016, SCH_USE_STRONG_CRYPTO option now disables NULL, MD5, DES, and export ciphers.

變更橢圓形曲線Elliptical Curve changes

Windows 10、1507 版和 Windows Server 2016 增加電腦設定] 下的橢圓形這些群組原則設定 > 系統管理範本] > 網路 > SSL 設定。Windows 10, version 1507 and Windows Server 2016 add Group Policy configuration for elliptical curves under Computer Configuration > Administrative Templates > Network > SSL Configuration Settings. ECC 曲線順序清單指定橢圓形曲線慣用的順序,以及可支援的曲線這不支援。The ECC Curve Order list specifies the order in which elliptical curves are preferred as well as enables supported curves which are not enabled.

新增下的橢圓形這些的支援:Added support for the following elliptical curves:

  • BrainpoolP256r1 (RFC 7027) Windows 10、1507 版和 Windows Server 2016 中BrainpoolP256r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
  • BrainpoolP384r1 (RFC 7027) Windows 10、1507 版和 Windows Server 2016 中BrainpoolP384r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
  • BrainpoolP512r1 (RFC 7027) Windows 10、1507 版和 Windows Server 2016 中BrainpoolP512r1 (RFC 7027) in Windows 10, version 1507 and Windows Server 2016
  • Curve25519 (RFC 草稿-ietf-tls-curve25519) Windows 10,版本 1607 年和 Windows Server 2016 中Curve25519 (RFC draft-ietf-tls-curve25519) in Windows 10, version 1607 and Windows Server 2016

適用於 SealMessage 與 UnsealMessage 發送層級支援Dispatch level support for SealMessage & UnsealMessage

Windows 10、1507 版和 Windows Server 2016 新增支援 SealMessage 日 UnsealMessage 發送層級。Windows 10, version 1507 and Windows Server 2016 add support for SealMessage/UnsealMessage at dispatch level.

DTLS 1.2DTLS 1.2

Windows 10,版本 1607 年和 Windows Server 2016 新增 DTLS 1.2 (RFC 6347) 的支援。Windows 10, version 1607 and Windows Server 2016 add support for DTLS 1.2 (RFC 6347).

HTTP.SYS 執行緒集區HTTP.SYS thread pool

Windows 10,版本 1607 年和 Windows Server 2016 新增登錄用來處理 TLS handshakes HTTP.SYS.Windows 10, version 1607 and Windows Server 2016 add registry configuration of the size of the thread pool used to handle TLS handshakes for HTTP.SYS.

登錄路徑:Registry path:

HKLM\SYSTEM\CurrentControlSet\Control\LSAHKLM\SYSTEM\CurrentControlSet\Control\LSA

若要指定每個 CPU 核心最大討論串中有集區大小,請建立MaxAsyncWorkerThreadsPerCpu的項目。To specify a maximum thread pool size per CPU core, create a MaxAsyncWorkerThreadsPerCpu entry. 此項目不存在於登錄預設。This entry does not exist in the registry by default. 您所建立的項目後,變更所需的大小 DWORD 值。After you have created the entry, change the DWORD value to the desired size. 如果未設定,最大值是每個 CPU 核心 2 執行緒。If not configured, then the maximum is 2 threads per CPU core.

下一步通訊協定交涉 (NPN) 的支援Next Protocol Negotiation (NPN) support

開始使用 Windows 10 版本 1703 年下, 一步通訊協定交涉 (NPN) 已移除,已不再支援。Beginning with Windows 10 version 1703, Next Protocol Negotiation (NPN) has been removed and is no longer supported.

預先共用的金鑰 (PSK)Pre-Shared Key (PSK)

Windows 10,版本 1607 年和 Windows Server 2016 新增 PSK 金鑰交換演算法 (RFC 4279) 的支援。Windows 10, version 1607 and Windows Server 2016 add support for PSK key exchange algorithm (RFC 4279).

新增的支援下列 PSK 密碼套件:Added support for the following PSK cipher suites:

  • TLS_PSK_WITH_AES_128_CBC_SHA256 (RFC 5487) Windows 10,版本 1607 年和 Windows Server 2016 中TLS_PSK_WITH_AES_128_CBC_SHA256 (RFC 5487) in Windows 10, version 1607 and Windows Server 2016
  • Windows 10,版本 1607 年和 Windows Server 2016 中 TLS_PSK_WITH_AES_256_CBC_SHA384(RFC 5487)TLS_PSK_WITH_AES_256_CBC_SHA384(RFC 5487) in Windows 10, version 1607 and Windows Server 2016
  • TLS_PSK_WITH_NULL_SHA256 (RFC 5487) Windows 10,版本 1607 年和 Windows Server 2016 中TLS_PSK_WITH_NULL_SHA256 (RFC 5487) in Windows 10, version 1607 and Windows Server 2016
  • TLS_PSK_WITH_NULL_SHA384 (RFC 5487) Windows 10,版本 1607 年和 Windows Server 2016 中TLS_PSK_WITH_NULL_SHA384 (RFC 5487) in Windows 10, version 1607 and Windows Server 2016
  • TLS_PSK_WITH_AES_128_GCM_SHA256 (RFC 5487) Windows 10,版本 1607 年和 Windows Server 2016 中TLS_PSK_WITH_AES_128_GCM_SHA256 (RFC 5487) in Windows 10, version 1607 and Windows Server 2016
  • TLS_PSK_WITH_AES_256_GCM_SHA384 (RFC 5487) Windows 10,版本 1607 年和 Windows Server 2016 中TLS_PSK_WITH_AES_256_GCM_SHA384 (RFC 5487) in Windows 10, version 1607 and Windows Server 2016

不伺服器端狀態伺服器端效能改進的工作階段回復Session Resumption without Server-Side State server-side performance improvements

Windows 10、1507 版和 Windows Server 2016 提供活動門票相較於 Windows Server 2012 30%更多工作階段 resumptions 秒。Windows 10, version 1507 and Windows Server 2016 provide 30% more session resumptions per second with session tickets compared to Windows Server 2012.

工作階段 Hash 和延伸的主要密碼擴充功能Session Hash and Extended Master Secret Extension

Windows 10、1507 版和 Windows Server 2016 新增支援 RFC 7627:傳輸層級的安全性 (TLS) 工作階段 Hash 和延伸的主要密碼擴充功能。Windows 10, version 1507 and Windows Server 2016 add support for RFC 7627: Transport Layer Security (TLS) Session Hash and Extended Master Secret Extension.

由於這項變更,Windows 10 與 Windows Server 2016 需要 3 廠商CNG SSL 提供者支援 NCRYPT_SSL_INTERFACE_VERSION_3,並描述這個新的介面的更新。Due to this change, Windows 10 and Windows Server 2016 requires 3rd party CNG SSL provider updates to support NCRYPT_SSL_INTERFACE_VERSION_3, and to describe this new interface.

SSL 支援SSL support

開始使用 Windows 10,版本 1607 年和 Windows Server 2016、TLS client 和伺服器 SSL 3.0 預設停用。Beginning with Windows 10, version 1607 and Windows Server 2016, the TLS client and server SSL 3.0 is disabled by default. 這表示應用程式或服務專門要求 SSPI 透過 SSL 3.0,除非 client 將不提供或接受 SSL 3.0,伺服器一律不會選取 SSL 3.0。This means that unless the application or service specifically requests SSL 3.0 via the SSPI, the client will never offer or accept SSL 3.0 and the server will never select SSL 3.0.

開始使用 Windows 10 版本 1607 年和 Windows Server 2016、SSL 2.0 已經移除,已不再支援。Beginning with Windows 10 version 1607 and Windows Server 2016, SSL 2.0 has been removed and is no longer supported.

變更 Windows TLS 遵守有不相容的 TLS 戶端 TLS 1.2 需求Changes to Windows TLS adherence to TLS 1.2 requirements for connections with non-compliant TLS clients

在 TLS 1.2 client 使用「signature_algorithms「擴充功能以指出伺服器可能會在數位簽章(亦即伺服器的憑證和 server 的關鍵換貨)中使用的簽章日 hash 演算法配對。In TLS 1.2, the client uses the "signature_algorithms" extension to indicate to the server which signature/hash algorithm pairs may be used in digital signatures (i.e., server certificates and server key exchange). TLS 1.2 RFC 也需要伺服器的憑證郵件接受」signature_algorithms」擴充功能:The TLS 1.2 RFC also requires that the server Certificate message honor "signature_algorithms" extension:

「Client 提供「signature_algorithms「擴充功能,如果然後伺服器提供所有憑證必須都登由該擴充中顯示的演算法對 hash 月簽章。」"If the client provided a "signature_algorithms" extension, then all certificates provided by the server MUST be signed by a hash/signature algorithm pair that appears in that extension."

實際上,某些第三方 TLS 戶端,請不要使用 TLS 1.2 RFC 和失敗包含所有的簽章和 hash 他們會接受在「signature_algorithms「擴充功能的演算法配對遵守或完全略過擴充功能(後者表示伺服器 client 僅支援 SHA1 RSA、DSA 或 ecdsa 來)。In practice, some third-party TLS clients do not comply with the TLS 1.2 RFC and fail to include all the signature and hash algorithm pairs they are willing to accept in the "signature_algorithms" extension, or omit the extension altogether (the latter indicates to the server that the client only supports SHA1 with RSA, DSA or ECDSA).

TLS 伺服器通常只有設定端點,這表示伺服器永遠不能提供的憑證,以符合 client 的需求每一個憑證。A TLS server often only has one certificate configured per endpoint, which means the server can’t always supply a certificate that meets the client’s requirements.

Windows 10 與 Windows Server 2016、Windows TLS 堆疊之前嚴格遵守 TLS 1.2 RFC 需求 RFC 不相容的 TLS 戶端與交互操作問題會導致連接失敗。Prior to Windows 10 and Windows Server 2016, the Windows TLS stack strictly adhered to the TLS 1.2 RFC requirements, resulting in connection failures with RFC non-compliant TLS clients and interoperability issues. 在 Windows 10 與 Windows Server 2016、限制的於輕鬆置於,以伺服器傳送 TLS 1.2 RFC,不符合憑證的是否伺服器的唯一的選項。In Windows 10 and Windows Server 2016, the constraints are relaxed and the server can send a certificate that does not comply with TLS 1.2 RFC, if that’s the server’s only option. Client 然後可能繼續或結束交換。The client may then continue or terminate the handshake.

驗證時 server 和 client 的憑證,Windows TLS 堆疊嚴格遵守 TLS 1.2 RFC,且只允許 server 和 client 憑證中的 [交涉簽章和 hash 演算法。When validating server and client certificates, the Windows TLS stack strictly complies with the TLS 1.2 RFC and only allows the negotiated signature and hash algorithms in the server and client certificates.