-
Notifications
You must be signed in to change notification settings - Fork 458
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
Language oblivious error handling leads to wrong exception being thrown #434
Comments
Just to confirm the report of weddige: performing {
"cipher_suite": {
"is_anonymous": false,
"key_size": 128,
"name": "TLS_RSA_WITH_RC4_128_SHA",
"openssl_name": "RC4-SHA"
},
"error_message": "Server closed the connection: received TCP FIN"
}, So the |
Thanks for figuring this out 👍 . I just pushed a fix - can you try it? Thanks! |
This looks good for me and it works in general. Nevertheless, I recognized one issue. When performing
This is due to https://github.com/nabla-c0d3/sslyze/blob/3.0.3/sslyze/plugins/session_renegotiation_plugin.py#L155-L163, where the same issue should be fixed in a similar way to de8c1da. A quick search for the appropriate keywords revealed no further code locations with the same issue. Thanks for the quick response and fix. Looking forward to Release 3.0.4! |
Thanks :). Just pushed the change for renegotiation - can you try it? Thanks! |
It works for me with multiple servers where I had problems before. No problems, no errors. 👍 Thanks for the help and the fixes! |
Released in v3.0.4. |
Describe the bug
This is a follow up to #430. I did some investigation into the issue and was able to locate a plausible cause for the crash.
To Reproduce
The issue is platform and language dependent.
The following code produces an exception on
but does not produce an exception on
The relevant part of the stack trace is:
This exception can be reproduced with the following code:
This raises an
ConnectionResetError
on both aforementioned platforms:[Errno 104] Connection reset by peer
(Linux)[WinError 10054] Eine vorhandene Verbindung wurde vom Remotehost geschlossen
(Win 10; german)Expected behavior
The expected behavior is identical behavior on all platforms.
Additional context
This leads to the following lines in sslyze as the likely cause of #430:
ServerRejectedTlsHandshake
is only raised if the error message matches one entry of_HANDSHAKE_REJECTED_SOCKET_ERRORS
, but this does not work with localized error messages.The text was updated successfully, but these errors were encountered: