Support for custom ciphers and protocols for https requests#381
Conversation
ryber
approved these changes
Nov 3, 2020
ryber
left a comment
Collaborator
There was a problem hiding this comment.
This looks great. I have a couple other things to work into a release, I'll probably cut it this weekend
Contributor
Author
|
Thank you very much! |
Collaborator
|
@Hakky54 there was an issue with the GitHub Actions setup for PRs would you mind rebasing your branch with master (or merge master, either way) |
Contributor
Author
|
I just merged your master branch with mine master branch and pushed the changes. Please let me know if something else needs to be done |
ryber
approved these changes
Nov 4, 2020
Collaborator
|
This is in 3.11.04 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request is an implementation for the following feature request: #380
Usage would be for example:
This will force your client to communicate over TLSv1.2 and TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 with the server or else it will fail. This setup will also prevent your client to communicate with older protocols such as TLSv1.1 and TLSv1