https://bugs.documentfoundation.org/show_bug.cgi?id=164781
--- Comment #6 from Patrick (volunteer) <[email protected]> --- (In reply to Noel Grandin from comment #5) > indicates that the macOS supports TLS1.3 I think TLS 1.3 is limited to the LibreSSL backend but that does not appear to be able to read certificates in the Keychain Access application. Using the following command (note that no backend is specified): /usr/bin/curl -v --tlsv1.3 --cert 'My Cert' 'https://bugs.documentfoundation.org/' ...I get the following error: curl: (4) A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. Using the following command with Secure Transport: CURL_SSL_BACKEND=secure-transport /usr/bin/curl -v --tlsv1.3 --cert 'My Cert' 'https://bugs.documentfoundation.org/' ...works, but I see the following in the output: * Client certificate: My Cert * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 > But yes, being stuck at TLS1.2 is a problem, servers will stop supporting > that at some point. So, from my limited testing, it looks like Secure Transport is stuck at TLS 1.2. Maybe switching to system libcurl may by us some time though until either the cURL developers or Apple implements some replacement for Secure Transport? -- You are receiving this mail because: You are the assignee for the bug.
