-
Notifications
You must be signed in to change notification settings - Fork 3k
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
{Packaging} Loosen cryptography
dependency
#19639
Conversation
cryptography
dependencycryptography
dependency
Packaging |
@glaubitz, I have totally removed the lower bound. Will this suit your need? |
Is version 3.0 actually the absolute minimum that you need now? That is, is there functionality that you need that is not part of version 2.8? |
We don't require >3.0 now. Any version works. |
Then either remove the version requirement or use at least 2.8 which is what SLE-12 and SLE-15 are shipping at the moment. |
It is already removed. |
Description
Reasons why we can loose the
cryptography
dependency now:For upper bound
#15687 (comment) set an upper bound for
cryptography
due to pyca/cryptography#5771.By following https://cryptography.io/en/latest/installation/#alpine, I am now able to install
cryptography
3.4.8 on Alpine Linux (#19591). There is no need to set upper bound now.For lower bound
Community packagers ask us not to bump the minimum dependency in
setup.py
as this causes trouble for platforms that doesn't support newer versions ofcryptography
(#15687 (comment)). By loosing the dependency oncryptography
, users or packagers themselves are now responsible for security vulnerabilities in older versions ofcryptography
.As we still pin the version in
requirements.*.txt
, packages distributed by us still containcryptography
which is security-complaint.