Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tls-cipher-suites-in-windows-10-v1903.md #1933

Merged
merged 2 commits into from
Oct 30, 2024
Merged

Update tls-cipher-suites-in-windows-10-v1903.md #1933

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
77dd188
Update tls-cipher-suites-in-windows-10-v1903.md
james-msft Oct 23, 2024
edb21f1
Update desktop-src/SecAuthN/tls-cipher-suites-in-windows-10-v1903.md
alvinashcraft Oct 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update desktop-src/SecAuthN/tls-cipher-suites-in-windows-10-v1903.md 
Adjusting URLs
  • Loading branch information
@alvinashcraft
alvinashcraft authored Oct 30, 2024
commit edb21f1c406a08b64afed48a48a8647bb0d3712c
2 changes: 1 addition & 1 deletion desktop-src/SecAuthN/tls-cipher-suites-in-windows-10-v1903.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Cipher suites can only be negotiated for TLS versions which support them. The hi
Availability of cipher suites are controlled by combining the two configurations below:

- LSA Configuration: Default priority order is overridden when a priority list is configured. Cipher suites not in the priority list will not be used.
- App Configuration: Applications can pass [SCHANNEL\_CRED](https://learn.microsoft.com/en-us/windows/win32/api/schannel/ns-schannel-schannel_cred) or [SCH\_CREDENTIALS](https://learn.microsoft.com/en-us/windows/win32/api/schannel/ns-schannel-sch_credentials) to specify the flags and enable (or disabled) specific protocols/algorithms during [AcquireCredentialsHandle (Schannel) function](https://learn.microsoft.com/en-us/windows/win32/secauthn/acquirecredentialshandle--schannel). More details can be referred at: [Creating a Secure Connection Using Schannel](https://learn.microsoft.com/en-us/windows/win32/secauthn/creating-a-secure-connection-using-schannel)
- App Configuration: Applications can pass [SCHANNEL\_CRED](/windows/win32/api/schannel/ns-schannel-schannel_cred) or [SCH\_CREDENTIALS](/windows/win32/api/schannel/ns-schannel-sch_credentials) to specify the flags and enable (or disabled) specific protocols/algorithms during [AcquireCredentialsHandle (Schannel) function](/windows/win32/secauthn/acquirecredentialshandle--schannel). More details can be referred at: [Creating a Secure Connection Using Schannel](/windows/win32/secauthn/creating-a-secure-connection-using-schannel)

> [!IMPORTANT]
> HTTP/2 web services fail with non-HTTP/2-compatible cipher suites. To ensure your web services function with HTTP/2 clients and browsers, see [How to deploy custom cipher suite ordering](/troubleshoot/windows-server/windows-security/deploy-custom-cipher-suite-ordering).
Expand Down