Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
CURLSSLOPT_ALLOW_UNSAFE_RENEG ?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 6 Aug 2023 23:37:34 +0200 (CEST)
Hello team,
I want to put your attention to the proposed PR #11559 which would introduce
the option in the subject.
Should we or should we not add this option?
This is a boolean option that when set, allows curl built to use OpenSSL to
deal with *unsafe* TLS renegotiations.
There are legacy servers out there that insist on using unsafe renegotiations.
curl using OpenSSL 3 will exit with an error when it runs into such a server.
Unless we introduce an option for users to allow this insecure protocol
detail.
See https://github.com/curl/curl/pull/11559 for the PR.
Date: Sun, 6 Aug 2023 23:37:34 +0200 (CEST)
Hello team,
I want to put your attention to the proposed PR #11559 which would introduce
the option in the subject.
Should we or should we not add this option?
This is a boolean option that when set, allows curl built to use OpenSSL to
deal with *unsafe* TLS renegotiations.
There are legacy servers out there that insist on using unsafe renegotiations.
curl using OpenSSL 3 will exit with an error when it runs into such a server.
Unless we introduce an option for users to allow this insecure protocol
detail.
See https://github.com/curl/curl/pull/11559 for the PR.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-08-06