From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFC v2 0/6] openssl: upgrade to 4.0.1 and fix dependent recipes
Date: Fri, 21 Aug 2026 22:17:29 +0100 [thread overview]
Message-ID: <9a98b9099e927565c0ed867b7598ccea9afdbfe4.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260820181022.44434-1-jaipaul.cheernam@est.tech>
On Thu, 2026-08-20 at 20:10 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> This series upgrades OpenSSL from 3.5.7 to 4.0.1 and fixes all
> dependent recipes that break due to API changes in OpenSSL 4.0.
>
> Changes since v1:
> - u-boot: moved patch from u-boot-tools_2026.07.bb to u-boot-common.inc
> so it applies to both u-boot and u-boot-tools (fixes riscv64 build
> failure reported from autobuilder)
> - u-boot, kea: corrected Upstream-Status from Backport to Submitted
> (neither has been merged upstream yet)
> - Dropped rust 1.97.1 from this series (now merged in master)
> - No external dependencies — wpa-supplicant 2.12 and rust 1.97.1
> are both merged in master now
>
> OpenSSL 4.0 is a major release with several breaking changes:
> - ENGINE API fully removed
> - SSLv3 support removed
> - Per-version TLS method functions (SSLv3_method etc.) removed
> - ASN1_STRING made opaque
> - const qualifiers added to X509 getter functions
>
> Patches:
> 1/6 openssl: upgrade 3.5.7 -> 4.0.1
> 2/6 python3: backport OpenSSL 4.0 support (CPython commit 3364e7e62fa2)
> 3/6 socat: fix ASN1_STRING opaque struct access
> 4/6 serf: fix ASN1_STRING opaque struct access
> 5/6 u-boot: backport Provider API (replaces removed ENGINE API)
> 6/6 kea: add const qualifiers to X509 pointers
>
> Testing:
> - bitbake world -k: passes on qemux86-64, qemuarm64, qemuarm, qemuriscv64
> - openssl ptest on qemux86-64: 362 files, 4310 tests, all passed
> (338 passed, 24 skipped - fips/lms/rc5/tfo/compression - all expected)
>
> Sharing this to get feedback and see if there are other recipes that
> break with OpenSSL 4.0 that we may have missed.
>
> Notes on upstream status:
> - python3: fix on CPython main, backport PR #146403 closed without merge
> - socat: submitted to socat@dest-unreach.org
> - serf: fix in trunk (r1935023), no release yet
> - u-boot: PR #918 open since March 2026, under review
> - kea: tracked as issue #4673, milestone kea3.3.2
>
> Jaipaul Cheernam (6):
> openssl: upgrade 3.5.7 -> 4.0.1
> python3: backport OpenSSL 4.0 support from upstream
> socat: fix build with OpenSSL 4.0
> serf: fix build with OpenSSL 4.0
> u-boot: fix build with OpenSSL 4.0
> kea: fix build with OpenSSL 4.0
Thanks for putting this together. It is definitely getting there but
there were some issues.
There are some failing selftests:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4629
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4449
and python ptest doesn't look happy:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4352
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1004
and multilib looks broken:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/92/builds/4423
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/4476
Nothing too unexpected with a change that invasive though!
Cheers,
Richard
next prev parent reply other threads:[~2026-08-21 21:17 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 5:18 [RFC 0/7] openssl: upgrade to 4.0.1 and fix dependent recipes Jaipaul Cheernam
2026-08-14 5:18 ` [PATCH 1/7] openssl: upgrade 3.5.7 -> 4.0.1 Jaipaul Cheernam
2026-08-15 16:20 ` [OE-core] " Mathieu Dubois-Briand
2026-08-14 5:18 ` [PATCH 2/7] python3: backport OpenSSL 4.0 support from upstream Jaipaul Cheernam
2026-08-14 5:18 ` [PATCH 3/7] socat: fix build with OpenSSL 4.0 Jaipaul Cheernam
2026-08-14 5:18 ` [PATCH 4/7] rust: Upgrade 1.96.1 -> 1.97.1 Jaipaul Cheernam
2026-08-15 16:11 ` [OE-core] " Mathieu Dubois-Briand
2026-08-14 5:18 ` [PATCH 5/7] serf: fix build with OpenSSL 4.0 Jaipaul Cheernam
2026-08-14 5:18 ` [PATCH 6/7] u-boot-tools: " Jaipaul Cheernam
2026-08-14 11:12 ` [OE-core] " Alexander Kanavin
2026-08-21 10:44 ` Quentin Schulz
2026-08-15 16:14 ` Mathieu Dubois-Briand
2026-08-14 5:18 ` [PATCH 7/7] kea: " Jaipaul Cheernam
2026-08-14 11:14 ` [OE-core] " Alexander Kanavin
2026-08-20 18:10 ` [RFC v2 0/6] openssl: upgrade to 4.0.1 and fix dependent recipes Jaipaul Cheernam
2026-08-20 18:10 ` [RFC v2 1/6] openssl: upgrade 3.5.7 -> 4.0.1 Jaipaul Cheernam
2026-08-21 17:52 ` [OE-core] " Khem Raj
2026-08-20 18:10 ` [RFC v2 2/6] python3: backport OpenSSL 4.0 support from upstream Jaipaul Cheernam
2026-08-20 18:10 ` [RFC v2 3/6] socat: fix build with OpenSSL 4.0 Jaipaul Cheernam
2026-08-20 18:10 ` [RFC v2 4/6] serf: " Jaipaul Cheernam
2026-08-20 18:10 ` [RFC v2 5/6] u-boot: " Jaipaul Cheernam
2026-08-21 10:52 ` [OE-core] " Quentin Schulz
2026-08-22 14:02 ` Jaipaul Cheernam
2026-08-20 18:10 ` [RFC v2 6/6] kea: " Jaipaul Cheernam
2026-08-21 21:17 ` Richard Purdie [this message]
2026-08-22 14:31 ` [OE-core][RFC v3 0/6] openssl: upgrade 3.5.7 -> 4.0.1 Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 1/6] " Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 2/6] python3: backport OpenSSL 4.0 support from upstream Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 3/6] socat: fix build with OpenSSL 4.0 Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 4/6] serf: " Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 5/6] u-boot: " Jaipaul Cheernam
2026-08-22 14:31 ` [OE-core][RFC v3 6/6] kea: " Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 0/6] openssl: upgrade 3.5.7 -> 4.0.1 Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 1/6] " Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 2/6] python3: backport OpenSSL 4.0 support from upstream Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 3/6] socat: fix build with OpenSSL 4.0 Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 4/6] serf: " Jaipaul Cheernam
2026-08-22 17:51 ` [RFC v4 5/6] u-boot: " Jaipaul Cheernam
2026-08-22 17:52 ` [RFC v4 6/6] kea: " Jaipaul Cheernam
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=9a98b9099e927565c0ed867b7598ccea9afdbfe4.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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