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

Jump to bottom

DEPRECATE.md: TLS libraries without 1.3 support #13544

Closed
wants to merge 2 commits into from
+10 −0
Closed

DEPRECATE.md: TLS libraries without 1.3 support #13544

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7dca689
DEPRECATE.md: TLS libraries without 1.3 support
bagder May 6, 2024
859c480
fixup mbedTLS has 1.3 now
bagder May 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/DEPRECATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,16 @@ email the
as soon as possible and explain to us why this is a problem for you and
how your use case cannot be satisfied properly using a workaround.

## TLS libraries without 1.3 support

curl drops support for TLS libraries without TLS 1.3 capability in May 2025.

It requires that a curl build using the library should be able to negotiate
and use TLS 1.3, or else it is not good enough.

As of May 2024, the libraries that need to get fixed to remain supported after
May 2025 are: BearSSL and Secure Transport.

## space-separated `NOPROXY` patterns

When specifying patterns/domain names for curl that should *not* go through a
Expand Down