-
Notifications
You must be signed in to change notification settings - Fork 92
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
Possible regression between 1.3.2 and 1.3.4 (DecodeError
/ HandshakeFailure
)
#139
Comments
Seems the server only supports TLS 1.0, which has been deprecated, and the newer version of |
no, it's not linked to the version. id3global is rejecting the curve extension ( |
Just to add another case here, I think this may be happening with other servers. I'm experiencing this with dynamodb connections:
|
Another day, another crazy TLS implementation. After an annoying debug session, it turns out that the other side is requiring the 0xC014 cipher (ECDHE_RSA_AES256CBC_SHA1) to be there, if the Elliptic curve extension is present. Despite having lots of other good choice, the other side fails with a very unhelpful (and probably wrong protocol wise) Adding the C014 cipher for both |
fixed in tls-1.3.6 |
@vincenthz thanks for the speedy update! I appreciate the effort in hunting down these weird edge cases out in the wild. |
@vincenthz Agreed; thanks for looking into and sorting this so expediently! |
When using
tls-1.3.2
andtls-debug-0.4.0
'stls-simpleclient
to connect to https://id3global.com I receive a response:Recently, when upgrading to Stackage LTS 5.10 and thereby
tls-1.3.4
, our code broke. Runningtls-simpleclient
fromtls-debug-0.4.1
, which usestls-1.3.4
(both are in LTS 5.10), the following error occurs:Any thoughts on what might be causing this/what may have changed/how we might work around or help resolve the issue?
The text was updated successfully, but these errors were encountered: