Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 2/2] openssl: Upgrade 4.0.3 -> 4.1.0
Date: Wed, 28 Oct 2026 18:04:23 +0100	[thread overview]
Message-ID: <DMGMUOASKXM3.1G2I8856314UZ@bootlin.com> (raw)
In-Reply-To: <20261027183424.11874-2-jaipaul.cheernam@est.tech>

On Tue Oct 27, 2026 at 7:34 PM CET, Jaipaul Cheernam wrote:
>   Release information [1]:
>
>   OpenSSL 4.1.0 is a feature release adding significant new functionality to OpenSSL.
>
>   This release incorporates the following potentially significant or incompatible changes:
>
>   - Added VC-WIN32-MSVC2013 and VC-WIN64A-MSVC2013 build targets to provide internal functions for bridging the gaps in C99 standard support that are present in MSVC 2013.
>   - Added optimized ML-DSA and ML-KEM NTT operations on ppc64le; optimized ML-DSA operations on x86_64; AVX-512-optimized SHAKE x4 operations for ML-DSA on x86_64; AVX-512 and VAES optimizations for AES-CBC
>   decryption on x86_64.
>   - Changed tsget utility to use Net::Curl::Easy (from the Net-Curl CPAN distribution) instead of the abandoned WWW::Curl::Easy. Users who rely on tsget should install Net::Curl::Easy before upgrading.
>   - Dropped Windows-on-Itanium (VC-WIN64I) and Windows CE (VC-CE) targets from Configurations.
>   - Dropped no-ecdsa and no-ecdh options from Configure, as these options did not really disable the implementations. Use no-ec to disable the elliptic curve support.
>
>   This release adds the following new features:
>
>   - Support for DTLS 1.3 (RFC 9147). Refer to the ossl-guide-dtlsv13(7) manual page for details.
>   - Support for RFC 8701 GREASE (Generate Random Extensions And Sustain Extensibility).
>   - DTLS support in the SSL listener API.
>   - Support for IKEV2 KDF.
>   - Initial support for the Elbrus2000 (e2k) architecture.
>
>   [1] https://github.com/openssl/openssl/blob/openssl-4.1/NEWS.md#major-changes-between-openssl-40-and-openssl-410-23-oct-2026
>
> - Refresh existing patches
> - Verified with world
> - Verified ptest python3-cryptography
>    TOTAL: 4650
>    PASS: 4443
>    FAIL: 0
>    ERROR: 0
>   TOTAL: 1  FAIL: 0
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---

Hi Jaipaul,

This looks better, but we still have one failure:

Failed ptests:
{'python3-pyopenssl': ['tests/test_ssl.py:TestMemoryBIO.test_memory_connect']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4828

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2026-10-28 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 18:35 [PATCH] openssl: Upgrade 4.0.3 -> 4.1.0 Jaipaul Cheernam
2026-10-27 14:37 ` [OE-core] " Mathieu Dubois-Briand
2026-10-27 18:34 ` [PATCH v2 1/2] python3-cryptography: backport InvalidTag fix for openssl 4.1.0 Jaipaul Cheernam
2026-10-27 18:34   ` [PATCH v2 2/2] openssl: Upgrade 4.0.3 -> 4.1.0 Jaipaul Cheernam
2026-10-28 17:04     ` Mathieu Dubois-Briand [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DMGMUOASKXM3.1G2I8856314UZ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=jaipaul.cheernam@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox