Open Ethanljf opened 4 years ago
Any plans to update to sslyze v3? cryptography seems to have a CVE which is solved in Cryptography 3.2, but sslyze v2.x pins the dependency to 2.5 and hence not updating to sslyze v3 technically means using cryptography package with vulnerability.
Checking in again if there are any plans to upgrade to a newer sslyze.
This is becoming something of an issue for us at Freedom of the Press Foundation as the version of cryptography
the existing dependency tree requires has been accumulating more known security issues. So far, fortunately, none of the issues have been problems for us, but someday one might be and we'd really like to be able to upgrade.
If it would speed things up, we'd be happy to volunteer some of our own engineering time to resolving this if you'd accept a pull request and, ideally, we could get some guidance from someone on your team :)
🐛 Bug Report
The latest changes to SSLYZE cause a few import issues within pshtt.py.
To Reproduce
Run pshtt in conjunction with the latest version of sslyze available via PIP
Expected behavior
Pshtt succesfully implements https_check() to figure out the reason an endpoint wouldn't verify.
Any helpful log output
Import errors stemming from pshtt.py
To resolve these issues, I recommend either pinning the sslyze requirement to a previous version or implementing the following changes:
Sslyze-related imports within pshtt.py should be as follows (to maintain existing functionality):
It is worth noting that the latest changes to sslyze support asynchronous scanning. However, to simply maintain existing asynchronous scanning, "https_check()" could be amended as follows: