• https://pypi.io/packages/source/c/cryptography/ (Download)

• python3

• (2021-02-15) Updated to version: py-cryptography-3.3.2
• (2020-09-24) Updated to version: py-cryptography-3.1.1
• (2020-08-02) Updated to version: py-cryptography-3.0
• (2020-06-12) Updated to version: py-cryptography-2.9.2
• (2019-11-08) Updated to version: py-cryptography-2.8
• (2019-04-19) Updated to version: py-cryptography-2.6.1
• (2019-01-30) Updated to version: py-cryptography-2.5
• (2018-08-11) Updated to version: py-cryptography-2.3
• (2018-04-23) Updated to version: py-cryptography-2.2.2
• (2018-02-12) Updated to version: py-cryptography-2.1.4

Log message:
update to py-cryptography (pyca) 3.3.2.
not moving to 3.4 yet because 1) we don't yet have setuptools-rust
which looks like it needs a pip update (which becomes py3 only),
and 2) we still have some py2 users of pyca:
devel/py-twisted                2+3 (2 is only used by telepathy-logger)
mail/mailpile                   2-only
security/py-openssl             2+3 (2 is only used by yubiserve, py-twisted)
security/py-paramiko            2+3 (2 used by several)
security/py-service_identity    2+3 (2 is only used by py-twisted)
security/py-axolotl             2+3, 2 not used
www/py-http_ece                 2+3, 2 not used
www/py-jwt                      2+3, 2 not used

Log message:
update to py-cryptography*-3.1.1

Log message:
Ensure py-cryptography is ready for LIBRESSL_HAS_TLS1_3
Instead of checking for LIBRESSL_HAS_TLS1_3 directly, check for
availability of TLS1_3_VERSION in case we're using LibreSSL as
requested by jsing.

Log message:
update to py-cryptography 3.0
drop maintainer

Log message:
switch my maintainer email addresses to my own domain

Log message:
bump REVISION; python 3 default changed to 3.8

Log message:
update to py-cryptography 2.9.2

Log message:
update to py-cryptography 2.8

Log message:
s/PERMIT_PACKAGE_CDROM/PERMIT_PACKAGE/ and some light whitespace tidying
in ports which I maintain

Log message:
bump all the py3 things, _SYSTEM_VERSION didn't quite work out how
we expected and it's easier|safer to do it this way than fiddle with
pkg_add now. thanks aja for update tests with a quick bulk.

Log message:
update to pyca cryptography 2.6.1

Log message:
Unbreak security/py-cryptography following the addition of DTLS methods.
ok tb@

Log message:
update to py-cryptography 2.5

Log message:
update to py-cryptography-2.3

Log message:
backport security fix for CVE-2018-10903

Log message:
Security fix for CVE-2018-10903, backported from the new 2.2.3 release
ok sthen@ (MAINTAINER)

Log message:
only needs gcc not g++

Log message:
only needs gcc not g++

Log message:
MFC compiler switch for gcc arches

Log message:
build with ports-gcc on !clang arches. may help gcc arches which currently
fail with "undefined symbol '__builtin_unreachable".

Log message:
update to py-cryptography-2.2.2

Log message:
const changes needed for X509_OBJECT_get0_X509

Log message:
fix following more libressl additions. getting rather dirty but not much
point cleaning up until we get further with additions. (also some of
the cffi parts can't cope with ifdefs, blearghh).

Log message:
update to py-cryptography-2.1.4

Log message:
shuffle py-cryptography's checks following addition of X509_VERIFY_PARAM_* functions
to libcrypto; the ifdef version number checks they're doing can't handle the case
when the functions actually exist.
this could be simplified by moving us to CRYPTOGRAPHY_OPENSSL_102_OR_GREATER if we
get suite b error codes / flags later.

Log message:
update to py-cryptography-1.7.1

Log message:
Another hack to unbreak py-cryptography (this time runtime rather than
build) following symbol list changes around the X509_VERIFY_PARAM_*
functions in libcrypto; based on a diff from phessler who found this the
hard way (and I think landry also ran into it with qgis).. OK phessler

Log message:
bump ports depending on python3 in security

Log message:
update to py-cryptography 1.5.3

Log message:
Add a hack to allow building py-cryptography following the VERIFY_PARAMS
changes in libressl.

Log message:
Unbreak after py-setuptools update. This makes use of MODPY_ABI_TAG
ok sthen@

Log message:
update to py-cryptography-1.5.2

Log message:
update to py-cryptography 1.4

Log message:
update to py-cryptography 1.4

Log message:
update to py-cryptography 1.3.4

Log message:
'cvs add' a patch that I missed; breakage reported by nigel

Log message:
update to py-cryptography 1.3.1

Log message:
update to py-cryptography 1.2.2

Log message:
update to py-cryptography 1.2.1

Log message:
update to py-cryptography 1.1.2

Log message:
update to py-cryptography / py-cryptography_vectors 1.1
take maintainer

Log message:
update to py-cryptography 1.0.2

Log message:
bump REVISION for setuptools dep change.

Log message:
unbreak py2.7 flavour. oops, pasted in a few too many lines when I was
manually fixing up the plists for multi-flavour, reported by espie

Log message:
update to py-cryptography 0.91, and patch to permit building with recent
libressl (py-cryptography was providing its own implementation of
EC_curve_nid2nist for libressl and for old openssl versions, this was
broken when libressl added it - since LIBRESSL_VERSION doesn't provide
anything useful for recognising this, simply delete the libressl check
from the ifdef).

Log message:
add missing WANTLIB