linux/poky.git/meta/recipes-devtools/python/python3-cryptography, branch yocto-4.0.23

python3-cryptography: Backport fix for CVE-2024-26130

2024-03-25T14:11:25+00:00

Upstream-Status: Backport from https://github.com/pyca/cryptography/commit/97d231672763cdb5959a3b191e692a362f1b9e55 (From OE-Core rev: 7864c4605cde4851df644dd1d2867bd28d155710) Signed-off-by: Vijay Anusuri Signed-off-by: Steve Sakoman

python3-cryptography: fix CVE-2023-49083

2023-12-12T14:20:34+00:00

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Calling `load_pem_pkcs7_certificates` or `load_der_pkcs7_certificates` could lead to a NULL-pointer dereference and segfault. Exploitation of this vulnerability poses a serious risk of Denial of Service (DoS) for any application attempting to deserialize a PKCS7 blob/certificate. The consequences extend to potential disruptions in system availability and stability. This vulnerability has been patched in version 41.0.6. References: https://nvd.nist.gov/vuln/detail/CVE-2023-49083 https://security-tracker.debian.org/tracker/CVE-2023-49083 (From OE-Core rev: 2d104f78cd13a10640bc284c7fc8358bf305279c) Signed-off-by: Narpat Mali Signed-off-by: Steve Sakoman

python3-cryptography: fix for CVE-2023-23931

2023-05-10T14:19:56+00:00

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8. (From OE-Core rev: 368e450c2d800790a05924519f34c579e28e9cbb) Signed-off-by: Narpat Mali Signed-off-by: Steve Sakoman

python3-cryptography: backport fix for leaky test

2022-04-10T07:31:17+00:00

The leaking test case has been fixed upstream, so backport the patch. (From OE-Core rev: 4705b8a724fe288a20f1a080e2796ea90f46c9fb) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

python3-cryptography: Fix ptest result handling

2022-03-17T16:44:33+00:00

We run the tests correctly, we just don't get individual test result reporting. Borrow the code from python3-bcrypt to handle this correctly and ensure the test pass/fail scores and individual test results are reported in a format we can read. (From OE-Core rev: 17b7dfc46f75f66854c1e540480ef19df6fc43a2) Signed-off-by: Richard Purdie

python3-cryptography: mark test_create_certificate_with_extensions as expected to fail

2022-03-16T08:48:08+00:00

This test causes OpenSSL to leak some memory. Until this is resolved in OpenSSL, mark the test as expected-to-fail. (From OE-Core rev: b32917b113df6dce0200d35dd1b539279635d524) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

python3-cryptography: move from meta-python

2022-03-16T08:48:08+00:00

* inherit new setuptools_rust class (which inherits new pyo3 class, which inherits cargo and python3-dir). * RDEPENDS on python3-pytest-subtests for ptest * Copy pyproject.toml for ptest as it defines the pytest.marker(s) needed * Use 'cargo bitbake' to generate the crate:// SRC_URIs - Needed some hacks to the Cargo.toml in src/rust/ to make this work (probably only package.repository was strictly required): [package] description = "cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, message digests, and key derivation functions." homepage = "https://github.com/pyca/cryptography" repository = "https://github.com/pyca/cryptography" * Add patches to src/rust/Cargo.toml to fix cargo errors including pem version * Add check-memfree.py to ptest to check for sufficient free memory (From OE-Core rev: 27bd134c899d00d93806ecb0a62ec3f30b1e6ec6) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie