Skip to content
This repository has been archived by the owner on Jan 27, 2022. It is now read-only.

READ THIS IF YOU WANT HELP #238

Open
Varbin opened this issue Aug 29, 2017 · 4 comments
Open

READ THIS IF YOU WANT HELP #238

Varbin opened this issue Aug 29, 2017 · 4 comments

Comments

@Varbin
Copy link

Varbin commented Aug 29, 2017

tl;dr: PyCrypto is dead. Switch to PyCryptodome (GitHub: /~https://github.com/Legrandin/pycryptodome PyPi: https://pypi.python.org/pypi/pycryptodome). Do not report any new bugs here!


As you may or may not have noticed, the last change to PyCrypto was made three five years ago.

The developers don't react to issues on the issue tracker anymore. This means PyCrypto is de facto dead. If you find problems and want them to be fixed consider following:

As a user or developer who uses software which requires PyCrypto:

  • Tell this to your application's developer to switch to PyCryptodome and tell them PyCrypto is dead.

As a developer who develops/maintains software depending on PyCrypto:

  • Consider switching to Pycryptodome - it's a well mantained fork and mostly compatible. If your problems persists report your problem to Pycryptodome's developer.

As a developer who wants to develop new software:

  • Do not use Pycrypto! Use Pycrpytodome or cryptography. PyCrypto is old and not maintained.

While this is not an official statement it represents the status quo.

@s-weigand
Copy link

s-weigand commented Feb 6, 2019

Since i was about to write @dlitz (repo owner) an email about this, I was wandering if any maintainer is still around to put this issues text on the repos frontpage, so people will get redirected to Pycrpytodome or cryptography or even make a PYPI release with that information. Life happens and projects get deprecated, but I feel sad to see recent PR's to a dead project, it's just a waste of well meant effort. 😢

So maybe just make it official 'the king is dead, long live the king'.

@cmcqueen
Copy link

cmcqueen commented Feb 6, 2019

It would be good if GitHub could come up with a general automatic mechanism for this, to automatically figure out when a parent project is dead, and which fork might be a suitable go-to. Ie don't show merely a list of forks, but show an indication of their activity. Ideally, a quick perusal of the list of forks would make it obvious which forks are active.

But in this case, Legrandin/pycryptodome isn't a direct fork of this project, so that mechanism wouldn't help. There is a Legrandin/pycrypto, but that hasn't had recent activity either. Does GitHub not support a fork+rename?

@avrajsri
Copy link

avrajsri commented Oct 6, 2019

pip uninstall crypto
Delete "crypto" Folder [C:\Users\AppData\Local\Programs\Python\Python37\Lib\site-packages]
pip install crypto
pip uninstall pycryptodome
pip install pycryptodome

pip uninstall pycryptodomex
pip install pycryptodomex
pip uninstall cryptography
pip install cryptography

Rename Folder "crypto" to "Crypto" [C:\Users\AppData\Local\Programs\Python\Python37\Lib\site-packages]

Then Use "from Crypto.Cipher import AES"

@Iiridayn
Copy link

Iiridayn commented Dec 2, 2019

Also has usability concerns: https://www.ieee-security.org/TC/SP2017/papers/161.pdf published in 2017.

Creamaster added a commit to Creamaster/payment_paybox that referenced this issue Jul 17, 2020
Creamaster added a commit to Creamaster/payment_paybox that referenced this issue Jul 17, 2020
cspollar added a commit to cspollar/wagalytics that referenced this issue Sep 30, 2020
Pycrypto is no longer maintained. pycryptodome is a (mostly) drop in replacement. See pycrypto/pycrypto#238
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants