PyCA cryptography 44.0.0 has been released to PyPI. cryptography includes
both high level recipes and low level interfaces to common cryptographic
algorithms such as symmetric ciphers, asymmetric algorithms, message
digests, X.509, key derivation functions, and much more. We support Python
3.7+, and PyPy3 7.3.10+.
Changelog (https://cryptography.io/en/latest/changelog/#v44-0-0):
* BACKWARDS INCOMPATIBLE: Dropped support for LibreSSL < 3.9.
* Deprecated Python 3.7 support. Python 3.7 is no longer supported by the
Python core team. Support for Python 3.7 will be removed in a future
cryptography release.
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL
3.4.0.
* macOS wheels are now built against the macOS 10.13 SDK. Users on older
versions of macOS should upgrade, or they will need to build cryptography
themselves.
* Enforce the RFC 5280 requirement that extended key usage extensions must
not be empty.
* Added support for timestamp extraction to the MultiFernet class.
* Relax the Authority Key Identifier requirements on root CA certificates
during X.509 verification to allow fields permitted by RFC 5280 but
forbidden by the CA/Browser BRs.
* Added support for Argon2id when using OpenSSL 3.2.0+.
* Added support for the Admissions certificate extension.
* Added basic support for PKCS7 decryption (including S/MIME 3.2) via
pkcs7_decrypt_der(), pkcs7_decrypt_pem(), and pkcs7_decrypt_smime().
-Paul Kehrer (reaperhulk)
M2Crypto is the rather complete Python wrapper for OpenSSL
featuring RSA, DSA, DH, EC, HMACs, X509 message digests,
symmetric ciphers; SSL functionality to implement clients and
servers; HTTPS extensions to Python’s httplib, urllib, and
xmlrpclib; unforgeable HMAC’ing AuthCookies for web session
management; FTP/TLS client and server; S/MIME. M2Crypto can also
be used to provide SSL for Twisted. Smartcards supported through
the Engine interface (to be removed in the next version).
Brief overview of the changelog, the
complete list is in CHANGES file
(https://git.sr.ht/~mcepl/m2crypto/tree/master/item/CHANGES):
- Moved development to Sourcehut https://sr.ht/~mcepl/m2crypto
and the communication to the email list
~mcepl/m2crypto(a)lists.sr.ht (GitLab project is kept R/O and
used for CI)
- Plenty of bug fixes and improvements in the build and testing
infrastrcture
- Started work on providing complete coverage with type hints
(including eventually for the binary C extension)
- Removed support for Python 2.7, the least tested version is
Python 3.6 and OpenSSL 1.1.1. The highest version tested is
3.13.
- A lot of playing with support of various implementations of
time_t on various platforms
- initial draft of documentation for migration to pyca/cryptography
- fix Read the Docs configuration (contributed kindly by Facundo
Tuesca)
- Remove dependency on parameterized and use unittest.subTest
instead.
- We still missing proper testing on MacOS (any help welcome!)
Now is the time to test, help with review, and complain about
whatever is wrong!
Happy security hacking!
Matěj
--
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
If you are not paying for it, you’re not the customer; you’re the
product being sold.
-- blue_beetle (2010-08-26)
http://www.metafilter.com/95152/Userdriven-discontent#3256046
On Wed Apr 3, 2024 at 2:41 PM CEST, Ralf Hildebrandt wrote:
> This is a probe to check if this list is still active.
Not much active, considering I have discovered this message only
now (and I had to import it from archive ;)).
> The last post dates back to Dec. 2020 and the list owner's mail address
> has been broken for months now (causing endless bounces).
>
> Would anybody be willing to step in as list admin/owner?
Why do we have two email lists for exactly the same (this and
cryptography-dev(a)python.org)?
Matěj
--
http://matej.ceplovi.cz/blog/, @mcepl@floss.social
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
To err is human, to purr feline.
