Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RFC v4 0/6] openssl: upgrade 3.5.7 -> 4.0.1
Date: Sun, 23 Aug 2026 08:02:40 +0100	[thread overview]
Message-ID: <7a100e486f8bcc7f48ec0073ccaa95fabeb8b59f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260822175200.57534-1-jaipaul.cheernam@est.tech>

On Sat, 2026-08-22 at 19:51 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> Upgrade OpenSSL from 3.5.7 to 4.0.1 and fix all dependent recipe
> breakages in oe-core.
> 
> OpenSSL 4.0 is a major version bump that removes the ENGINE API,
> removes the c_rehash script, makes ASN1_STRING fully opaque, adds
> const qualifiers to X509 accessor return types, and removes
> per-version TLS method functions.
> 
> This series fixes python3, socat, serf, u-boot, and kea to build
> against OpenSSL 4.0.
> 
> Changes since v3:
>   - u-boot: fix malformed patch (hunk line count mismatch from pkcs11
>     modification). Regenerated patch properly.
> 
> Changes since v2:
>   - openssl: remove c_rehash from MULTILIB_SCRIPTS and FILES (fixes
>     multilib do_package failure)
>   - python3: add backports from CPython PR #149783 for the
>     got_eof_error fix (fixes test_https/test_https_sni ptest failures
>     caused by OpenSSL 4.0 changing EOF signaling behavior)
>   - u-boot: update Upstream-Status to lore link per reviewer feedback,
>     include doc/Dockerfile hunks from upstream v4, make pkcs11
>     provider loading optional (fixes fitimage signing failure when
>     pkcs11-provider is not installed)
> 
> Changes since v1:
>   - u-boot: move patch from u-boot-tools to u-boot-common.inc (fixes
>     riscv64 build failure)
>   - serf/socat: fix Upstream-Status tags

Thanks, definitely getting better!

There was one failure in core I spotted in barebox:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4689

I think that is openssl related but it is hard to be 100% sure.

Cheers,

Richard



      parent reply	other threads:[~2026-08-23  7:02 UTC|newest]

Thread overview: 42+ 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   ` [OE-core] [RFC v2 0/6] openssl: upgrade to 4.0.1 and fix dependent recipes Richard Purdie
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-23  6:56     ` [OE-core] " Khem Raj
2026-08-23  6:57       ` Khem Raj
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
2026-08-23  7:02   ` Richard Purdie [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=7a100e486f8bcc7f48ec0073ccaa95fabeb8b59f.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