-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ciphers to SSL options #1581
Comments
As a general rule, we only add new In this case, we know
@womblep I hope this can help getting you started. Would you have time to go through the other Faraday adapters and check how many of them support it? |
Excon - support
HTTPClient - support
Net::HTTP::Persistent - support
Patron - the adapter doesnt look like it does any SSL options other than verify. The Patron gem doesnt look like it supports ciphers (or many SSL settings) HTTP.rb adapter and gem use OpenSSL SSLContext which support ciphers
httpx - uses OpenSSL SSLContext so should be able to be added to the adapter in "def ssl_options_from_env(env)" |
Typhoeus - supported using ssl_cipher_list
Async::HTTP - supported - I am getting lost in the adapter but I think all the SSL options are passed through Async::HTTP::Faraday::Clients.make_client. Ciphers would be passed through without any change required. EM::HTTP - supported using cipher_list
|
This was great research, thank you ❤️! |
@womblep FYI – just released Faraday 2.11.0 with support for ciphers (and updated dependency on the |
@iMacTia thanks for the speedy release! ❤️ |
I have hit a server where I needed to pin the ciphers to be able to connect. The server is most certainly badly configured but it is not something I can get changed.
I was able to work around this by monkey-patching Faraday and the Faraday Net::HTTP adapter (Net::HTTP supports ciphers) but I would like to submit patches to make it easier to do.
The Faraday change is just adding a "ciphers" member to the SSLOptions
Linked to lostisland/faraday-net_http#44
The text was updated successfully, but these errors were encountered: