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
Unable to negotiate acceptable set of security parameters #9452
Comments
Can you please post the error message displayed. |
Here are the steps - including identical P12 certs, environments and credentials. |
Definitely doesn't work across multiple machines. I'd be interested to try the steps that work after version 4.7. Appreciate the time. |
|
Can you please share the hostname of the server. This will allow us to debug the SSL negotiation. |
Happy to provide, but would rather not do it on a publicly accessable site - shoot me an email? chouser@pfsweb.com |
|
|
Looks like a server configuration issue. Chrome.app also complains with |
I'm now able to reproduce the issue but the exact reason is not clear yet. We need some more time to investigate. |
We've noticed an increase in "inoperability failures" when connecting to secure webdav using P12's generated as part of our 2FA requirement when connecting to our SaaS based web platform. The login process never transfers from the certificate selection to allowing access to the key chain.
We've tracked it by trial/error to a change somewhere between version 4.7.3 (works) and 4.8.1 (failures)
Same remote webdav host/path and credentials and P12's used in all tests.
Here are the OpenSSL commands used to create the P12 (if this helps at all...)
I did notice that 4.8.1 was the first to have this:
[Bugfix] Restore compatibility with OS X 10.7 - 10.9 (Mac)
but unsure if that excludes versions 10.9.5 and higher... couldn't find a trac number to research further.
Attachments
Error Messsage Steps.docx
(1173.0 KiB)Handshake Failure.png
(78.6 KiB)The text was updated successfully, but these errors were encountered: