Skip to content
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

Why use pycryptodome < 3.4 ? #2

Open
RacingTadpole opened this issue Feb 28, 2018 · 4 comments
Open

Why use pycryptodome < 3.4 ? #2

RacingTadpole opened this issue Feb 28, 2018 · 4 comments

Comments

@RacingTadpole
Copy link

setup.py specifies pycryptodome >=3.3.1, <3.4.0. The latest version of pycryptodome is 3.4.11 (see the pycryptodome changelog).
Is there a reason not to use 3.4.11?

@adilosa
Copy link

adilosa commented Aug 29, 2018

FWIW, this now fails pipenv check due to a security vulnerability

$ pipenv check
Checking installed package safety...
36384: pycryptodome <3.6.6 resolved (3.3.1 installed)!
pycryptodome before 3.6.6 has a vulnerability on AESNI ECB with payloads smaller than 16 bytes.

@Illizion
Copy link

lol this is the only reason i need to fork this repo cough first fork cough, because i'm building an application, that because of GDPR, needs security, not failure

@Illizion
Copy link

i basically just need to fork it and substitute in the newer dependency

@diraven
Copy link

diraven commented May 30, 2019

There seems to be no movement on the issue for quite a while. Are there any restrictions that do not allow using newer versions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants