feat: enable legacy openssl providers + weak ciphers support #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update: Reverted this commit - see
Note for posterity
on Kong/insomnia#8192 (comment)Update2: If we have a need for looking into this again, see about how we can enable legacy providers and weak ciphers here https://github.com/JCMais/curl-for-windows/tree/master/openssl and if we need to fork that.
trying to fix Kong/insomnia#5059 and other similar issues where folks use weak/deprecated/old ciphers
some investigation: