use cryptodome instead of pycrypto
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Invalid
|
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-
following is more info:
pycryptodome:
http://
pyca/cryptography:
http://
I see pycrypto has not been developed since 2014.
https:/
https:/
In the future, the pycrypto will be drop and use cryptotodome instead.
here is the comments in the `global-
# 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-
Just leave this pycrypto here now.
Changed in kolla: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in kolla: | |
milestone: | none → ocata-3 |
summary: |
- use cryptotodome instead of pycrypto + use cryptodome instead of pycrypto |
Changed in kolla: | |
status: | Confirmed → Invalid |
milestone: | ocata-3 → none |