We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Sslyze does not scan multiple hosts in any case.
To Reproduce Steps to reproduce the behavior:
sslyze.exe --regular google.de google.com
> sslyze.exe --regular google.de google.com CHECKING HOST(S) AVAILABILITY ----------------------------- google.de:443 => 172.217.18.99 google.com:443 => 172.217.21.238 SCAN RESULTS FOR GOOGLE.DE:443 - 172.217.18.99 ---------------------------------------------- * OpenSSL Heartbleed: OK - Not vulnerable to Heartbleed ...
(In this case SCAN RESULTS FOR GOOGLE.COM:443 was missing)
SCAN RESULTS FOR GOOGLE.COM:443
This does not always happen, but I could reproduce it with google.de and google.com. With other domains it worked fine.
google.de
google.com
Expected behavior All hosts are scanned.
Python environment (please complete the following information):
Additional context I didn't investigate the issue further yet. More information may follow in the next days if necessary.
The text was updated successfully, but these errors were encountered:
[#429] Fix logic for clearing completed scans
1138cb3
Thanks for the report
Sorry, something went wrong.
[#429] Fix order of deletion of completed scans
74ff239
Fix released in v3.0.2.
No branches or pull requests
Describe the bug
Sslyze does not scan multiple hosts in any case.
To Reproduce
Steps to reproduce the behavior:
sslyze.exe --regular google.de google.com
(In this case
SCAN RESULTS FOR GOOGLE.COM:443
was missing)This does not always happen, but I could reproduce it with
google.de
andgoogle.com
. With other domains it worked fine.Expected behavior
All hosts are scanned.
Python environment (please complete the following information):
Additional context
I didn't investigate the issue further yet. More information may follow in the next days if necessary.
The text was updated successfully, but these errors were encountered: