Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Adding support for --ciphers in WinSSL/Schannel... #2630
Adding support for selecting ciphers in WinSSL/Schannel. Given the
To use this from the commandline, you need to pass the names of contants
curl --ciphers "CALG_SHA_256:CALG_RSA_SIGN:CALG_RSA_KEYX:CALG_AES_128:CALG_DH_EPHEM" https://github.com
The specific names come from wincrypt.h
This is an attempt to implement
…ntstraints of SChannel, I'm exposing these as the algorithms themselves instead; while replicating the ciphersuite as specified by OpenSSL would have been preferable, I found no way in the SChannel API to do so. To use this from the commandline, you need to pass the names of contants defining the desired algorithms. For example, curl --ciphers "CALG_SHA1:CALG_RSA_SIGN:CALG_RSA_KEYX:CALG_AES_128:CALG_DH_EPHEM" https://github.com The specific names come from wincrypt.h
I'm not sure how, but my documentation change seems to have caused a unit test to fail for the wolfssl debug build:
test 1455...[HTTP GET when PROXY Protocol enabled]
Is this known flakiness, or have I broken something clever?