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
RuntimeError with sslv2 #319
Comments
I am also observing same issue. Below is snippet of output. Can I consider this as below ciphers are not accepted.
Thanks, |
@swarooppatra, I don't think it means the ciphers are not accepted necessarily. It could be an internal error, but I haven't been able to track down the exact cause yet. |
Thanks @jsf9k. |
Fixed in eeffed5 |
Thanks @nabla-c0d3! |
Thanks @nabla-c0d3 . Can you please let me know which version of sslyze will have this feature. I just updated to 1.4.3 and I see same error. Thanks for this tool. |
It will be released with v2.0.0. |
Released as part of 2.0.0. |
As you can see below, I am consistently getting a
RuntimeError - A socket was already set
message when running this command:Is this expected? I'm using the latest
sslyze
code in themaster
branch and the latestnassl
from PyPI.The text was updated successfully, but these errors were encountered: