diff options
| author | Brad King <brad.king@kitware.com> | 2024-05-09 13:01:46 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2024-05-09 18:58:06 (GMT) |
| commit | d3cbee99e3c998d5821add091b426661f09f19f8 (patch) | |
| tree | aae811a093a1055e2a789860ad42f83488ae59dc /Source/cmConvertMSBuildXMLToJSON.py | |
| parent | d224c018fe807a733b82973214782e5c24c1ce76 (diff) | |
| download | CMake-d3cbee99e3c998d5821add091b426661f09f19f8.zip CMake-d3cbee99e3c998d5821add091b426661f09f19f8.tar.gz CMake-d3cbee99e3c998d5821add091b426661f09f19f8.tar.bz2 | |
macOS: Prefer building with system-provided curl
Our vendored curl only enables the Secure Transport backend by default
(`CURL_SSL_BACKEND=secure-transport`), but it is limited to TLS 1.2.
The macOS SDK provides the curl development components, and the
corresponding `libcurl.4.dylib` runtime library comes with macOS.
On macOS 12 and above, the default `CURL_SSL_BACKEND=openssl`
backend seems to be capable of selecting TLS 1.3 at runtime for
https connections.
Unfortunately the macOS version of curl, even on macOS 14.4, does
not accept `CURL_SSLVERSION_TLSv1_3` at runtime to enforce TLS 1.3.
However, while our vendored curl accepts the option and passes it
to Secure Transport, macOS does not actually enforce it anyway.
Fixes: #25870
Fixes: #23701
Diffstat (limited to 'Source/cmConvertMSBuildXMLToJSON.py')
0 files changed, 0 insertions, 0 deletions