<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/python/python3-cryptography, branch yocto-4.0.14</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-4.0.14</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-4.0.14'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2023-05-10T14:19:56+00:00</updated>
<entry>
<title>python3-cryptography: fix for CVE-2023-23931</title>
<updated>2023-05-10T14:19:56+00:00</updated>
<author>
<name>Narpat Mali</name>
<email>narpat.mali@windriver.com</email>
</author>
<published>2023-05-05T16:53:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1367249c996394668eaf97404874d7d13225a53d'/>
<id>urn:sha1:1367249c996394668eaf97404874d7d13225a53d</id>
<content type='text'>
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 &lt;narpat.mali@windriver.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>python3-cryptography: backport fix for leaky test</title>
<updated>2022-04-10T07:31:17+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross@burtonini.com</email>
</author>
<published>2022-04-08T13:38:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8b4a654641761298db1f47a8203fe12604382d13'/>
<id>urn:sha1:8b4a654641761298db1f47a8203fe12604382d13</id>
<content type='text'>
The leaking test case has been fixed upstream, so backport the patch.

(From OE-Core rev: 4705b8a724fe288a20f1a080e2796ea90f46c9fb)

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3-cryptography: Fix ptest result handling</title>
<updated>2022-03-17T16:44:33+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-03-17T00:32:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c075d001606e4d9645c79c522688fa067f2edfa6'/>
<id>urn:sha1:c075d001606e4d9645c79c522688fa067f2edfa6</id>
<content type='text'>
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 &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3-cryptography: mark test_create_certificate_with_extensions as expected to fail</title>
<updated>2022-03-16T08:48:08+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2022-03-14T13:56:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a5d252eea3e5a1196d1c72bfdeef4c61b898cedb'/>
<id>urn:sha1:a5d252eea3e5a1196d1c72bfdeef4c61b898cedb</id>
<content type='text'>
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 &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>python3-cryptography: move from meta-python</title>
<updated>2022-03-16T08:48:08+00:00</updated>
<author>
<name>Tim Orling</name>
<email>tim.orling@konsulko.com</email>
</author>
<published>2022-03-12T20:53:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c6f79207f8183eb3ec366dff39df070563e0e6e2'/>
<id>urn:sha1:c6f79207f8183eb3ec366dff39df070563e0e6e2</id>
<content type='text'>
* 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 &lt;tim.orling@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
