Skip to content

Update links to Mozilla's TLS guidelines. #97

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

Merged
jorritn merged 1 commit into from
Jul 13, 2026
+2 −2
Merged

Update links to Mozilla's TLS guidelines. #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions website/docs/learn/communication-layer/accepted-crypto.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebar_position: 4

The S2 Connect specification contains a description of encryption requirements. Because the security levels given by different crypto algorithms change continuously, this page contains the accepted crypto algorithms for S2 Connect. Keep in mind that this will change over time.

At the moment, we refer to the Mozilla guidelines in: [Server Side TLS](https://wiki.mozilla.org/Security/Server_Side_TLS). In the future these Mozilla guidelines will change, and S2 might have it's own list of accepted algorithms.
At the moment, we refer to the TLSRef guidelines in: [Server Side TLS](https://docs.tlsref.org/server-side-tls.html). In the future these Mozilla guidelines will change, and S2 might have it's own list of accepted algorithms.

## Accepted algorithms will change

Expand All @@ -17,4 +17,4 @@ Therefore, this list will continuously change, and kept up to date. However, to

## Accepted algorithms

At the moment, we consider the guidelines give by Mozilla in [Server Side TLS](https://wiki.mozilla.org/Security/Server_Side_TLS) on the level **Modern** as secure for usage in S2.
At the moment, we consider the guidelines give by TLSRef in [Server Side TLS](https://docs.tlsref.org/server-side-tls.html) on the level **Modern** as secure for usage in S2.