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

Change dependency from pycrypto #653

Closed
alanyee opened this issue May 10, 2019 · 1 comment
Closed

Change dependency from pycrypto #653

alanyee opened this issue May 10, 2019 · 1 comment
Assignees
Labels
type: process A process-related concern. May include testing, release, or the like.

Comments

@alanyee
Copy link

alanyee commented May 10, 2019

Is your feature request related to a problem? Please describe.
Pycrypto has not been maintained since 2014. So it susceptible to vulnerabilities like CVE-2013-7459 and CVE-2018-6594, and lacks some compatibility with the latest versions of python. Thus should not be in the tox file, documentation, etc.
Describe the solution you'd like
Replace pycrypto with an active, well-maintained python crypto library for development and testing
Describe alternatives you've considered
pycryptodome is "an almost drop-in replacement for the old PyCrypto library", but other libraries can still be considered.

@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label May 11, 2019
@busunkim96 busunkim96 added type: process A process-related concern. May include testing, release, or the like. and removed triage me I really want to be triaged. labels May 13, 2019
@busunkim96 busunkim96 self-assigned this Jun 10, 2019
@parthea
Copy link
Contributor

parthea commented Dec 8, 2020

Hi @alanyee,

I'm going to close this issue as pycrypto was removed in #799 .

@parthea parthea closed this as completed Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants