use cryptotodome instead of pycrypto

Bug #1565583 reported by Jeffrey Zhang on 2016-04-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Wishlist
Unassigned

Bug Description

the pycrypto is out of maintain. We should move to a fork of pycrypto: cryptodome.

But not all the packages required by OpenStack has to this kind of migration. So we should hold on this until the cryptodome is added to global-requirements.txt file.

following is more info:

pycryptodome:
http://lists.openstack.org/pipermail/openstack-dev/2016-February/086509.html

pyca/cryptography:
http://lists.openstack.org/pipermail/openstack-dev/2016-February/086586.html

I see pycrypto has not been developed since 2014.
https://pypi.python.org/pypi/pycrypto
https://github.com/dlitz/pycrypto

In the future, the pycrypto will be drop and use cryptotodome instead.
here is the comments in the `global-requirements.txt` file.
# NOTE(dims): pysaml 4.0.3 uses pycryptodome instead of pycrypto, for mitaka
# we cannot switch to pycryptodome as many projects are likely to break. So
# we should block versions higher then 4.0.2. Also, once all projects and
# dependencies like paramiko switch to pycryptodome, we should revisit this
# and fully switch over to pycryptodome and stop using pycrypto

So I think we should not move to pycrytodome until it is added to the global-requirements.txt.
Just leave this pycrypto here now.

Changed in kolla:
status: New → Confirmed
importance: Undecided → Wishlist
Changed in kolla:
milestone: none → ocata-3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers