11 Commits

Author SHA1 Message Date
jasper
c319cf3b5b update to py-cryptodome-3.7.3 2019-01-27 15:06:04 +00:00
naddy
84174f9106 bump for package path change devel/gmp -> devel/gmp,-main 2018-11-02 18:48:39 +00:00
jasper
f6998f3de8 security update to py-cryptodome-3.6.6 addressing CVE-2018-15560 2018-09-03 14:52:23 +00:00
jasper
77e8942ee5 update to py-cryptodome-3.6.4 2018-07-11 07:42:46 +00:00
jasper
e4f89180b0 update to py-cryptodome-3.6.3 2018-07-09 10:35:55 +00:00
sthen
572ba35c55 Use AESNI_COMMENT for _ghash_clmul.so as well; again x86 only and related
(though not exactly the same) as aes-ni things. From Markus Hennecke.
2018-06-24 11:46:58 +00:00
jasper
1453381730 update to pycryptodome-3.6.2 2018-06-23 11:52:30 +00:00
jasper
2db3c48215 remove stale comment 2018-06-23 11:35:07 +00:00
jasper
19b8b3bd4a make py-cryptodome a replacement for py-crypto. as an actively developed fork of py-crypto
it's almost a drop-in replacement https://www.pycryptodome.org/en/latest/src/vs_pycrypto.html

this commit effectively switches from the 'Cryptodome' namespace to 'Crypto'

feedback and ok sthen@
2018-06-02 11:47:13 +00:00
sthen
a78015aa89 Unbreak py-cryptodome on !x86 by using an arch-dependent subst'ed @comment
in the PLIST for the AES-NI related .so file. Reported by landry@,
ok landry jasper
2018-05-14 16:43:33 +00:00
jasper
480d231c41 import py-cryptodomex-3.6.1
PyCryptodome is a self-contained Python package of low-level cryptographic
primitives. It is an cleaned and simplified fork of PyCrypto, exposing
almost the same API. Most applications run unmodified, apart from a very
few compatibility breaks for those parts of the API that represented a
security hazard or that were too hard to maintain.

NB: currently we're packaging cryptodomex which doesn't conflict with py-crypto.
once all callers are migrated we can switch to the regular cryptodome package.

with and ok sthen@
2018-04-29 08:55:50 +00:00