From laurent.philippart at nokia.com Thu May 25 13:36:57 2023 From: laurent.philippart at nokia.com (Laurent Philippart (Nokia)) Date: Thu, 25 May 2023 17:36:57 +0000 Subject: [Cryptography-dev] openssl library Message-ID: Hi, Could you please clarify if cryptography is statically linked to openssl / libcrypto library or use the system's shared library ? I am interested in tracing calls to functions like "EVP_EncryptInit_ex" and "EVP_CipherInit_ex" for malware detection. However it seems that cryptography is not making use of the "libcrypto.so.1.1" shared library. Best regards Laurent -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex.gaynor at gmail.com Thu May 25 13:39:39 2023 From: alex.gaynor at gmail.com (Alex Gaynor) Date: Thu, 25 May 2023 13:39:39 -0400 Subject: [Cryptography-dev] openssl library In-Reply-To: References: Message-ID: Cryptography can be built to link OpenSSL in either mode. Our pre-built wheels statically link OpenSSL, but users can compile it either way. Alex On Thu, May 25, 2023, 1:38 PM Laurent Philippart (Nokia) < laurent.philippart at nokia.com> wrote: > Hi, > > > > Could you please clarify if cryptography is statically linked to openssl / > libcrypto library or use the system?s shared library ? > > > > I am interested in tracing calls to functions like ?EVP_EncryptInit_ex? > and ?EVP_CipherInit_ex? for malware detection. > > However it seems that cryptography is not making use of the > ?libcrypto.so.1.1? shared library. > > > > Best regards > > Laurent > > > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mass.shock57 at gmail.com Fri May 26 11:18:00 2023 From: mass.shock57 at gmail.com (Masoud Shokohi) Date: Fri, 26 May 2023 18:48:00 +0330 Subject: [Cryptography-dev] Submission Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Tue May 30 18:35:28 2023 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Wed, 31 May 2023 06:35:28 +0800 Subject: [Cryptography-dev] PyCA cryptography 41.0.0 released Message-ID: PyCA cryptography 41.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, X509, key derivation functions, and much more. We support Python 3.7+, and PyPy3 7.3.10+. Changelog (https://cryptography.io/en/latest/changelog/#v41-0-0): * BACKWARDS INCOMPATIBLE: Support for OpenSSL less than 1.1.1d has been removed. Users on older version of OpenSSL will need to upgrade. * BACKWARDS INCOMPATIBLE: Support for Python 3.6 has been removed. * BACKWARDS INCOMPATIBLE: Dropped support for LibreSSL < 3.6. * Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.1. * Updated the minimum supported Rust version (MSRV) to 1.56.0, from 1.48.0. * Added support for the OCSPAcceptableResponses OCSP extension. * Added support for the MSCertificateTemplate proprietary Microsoft certificate extension. * Implemented support for equality checks on all asymmetric public key types. * Added support for aes256-gcm at openssh.com encrypted keys in load_ssh_private_key(). * Added support for obtaining X.509 certificate signature algorithm parameters (including PSS) via signature_algorithm_parameters(). * Support signing PSS X.509 certificates via the new keyword-only argument rsa_padding on sign(). * Added support for ChaCha20Poly1305 on BoringSSL. -Paul Kehrer (reaperhulk)