-
Notifications
You must be signed in to change notification settings - Fork 80
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
Installation fails due to conflicting cryptography version #208
Comments
Suggested SolutionAsk your upstream project sslyze to loose the version range of cryptography. @konklone Could I submit a PR to solve this issue? |
This is an open issue for sslyze, but it appears to be marked for the eventual 3.0 release per the project board. Comments on the issue show no run issues, but feel free to submit a PR for review. |
Looks like sslyze v3 has been released but it still does complain when cryptography is above 2.8 |
sslyze 3.0.2 appears to have fixed this. |
I just did a clean venv and did a pip install of pshtt. Now its complaining this way. |
I have a similar problem wherein the
|
Hi, users are unable to run pshtt due to dependency conflict with cryptography package. As shown in the following full dependency graph of pshtt, pyopenssl requires cryptography >=2.8,while sslyze requires cryptography ==2.5.
According to pip’s “first found wins” installation strategy, cryptography 2.8 is the actually installed version. However, cryptography 2.8 does not satisfy ==2.5.
Dependency tree-----------
Thanks for your help.
Best,
Neolith
The text was updated successfully, but these errors were encountered: