Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
	 Dario Binacchi <dario.binacchi@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/libressl: security bump version to 4.3.2
Date: Tue, 20 Oct 2026 22:59:34 +0200	[thread overview]
Message-ID: <atfV3uwCqo4u7Hhq@windsurf> (raw)
In-Reply-To: <20260912202448.1673161-2-bernd@kuhls.net>

On Sat, Sep 12, 2026 at 10:24:47PM +0200, Bernd Kuhls wrote:
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.0.0-relnotes.txt
> "- The mips32 platform is no longer actively supported."
> 
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.0.1-relnotes.txt
> Fixes CVE-2025-9230.
> 
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.1.0-relnotes.txt
> "- Fixed compilation for mips32 and reenable CI."
> 
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.1.1-relnotes.txt
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.1.2-relnotes.txt
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.2.0-relnotes.txt
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.3.0-relnotes.txt
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.3.1-relnotes.txt
> 
> https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-4.3.2-relnotes.txt
> "This is the first stable release of the 4.3.x branch"
> 
> Rebased patch 0001.
> Removed patch 0002 which is included in this release.
> 
> Updated license hash due to upstream commit
> https://github.com/libressl/portable/commit/30598098a5df3059332327fa0c2bb5877740ac5d
> 
> Force OpenSSL for sscep due to the usage of NCONF_default()[1] which
> was removed from LibreSSL 4.0.0:
> https://github.com/libressl/openbsd/commit/646547a8a28c7b6931751a2ab064fd70d5d8cf92
> 
> and will cause build errors with this bump.
> 
> [1] https://github.com/certnanny/sscep/blob/v0.10.0/src/configuration.c#L37
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Thanks, applied!

> Series passed Gitlab pipelines:
> https://gitlab.com/bkuhls/buildroot/-/commits/834ad4accb3fc6eaef48724509c893431e9d0c67
> 
> with the exception of bootlin-aarch64-glibc-old:
> https://gitlab.com/bkuhls/buildroot/-/jobs/16464936859
> 
>   ./.libs/libfreeswitch.so: undefined reference to `getentropy'
> 
> Freeswitch added the usage of getentropy in version 1.11.0:
> https://github.com/signalwire/freeswitch/commit/7f9dd270b492907ddd063be18003e18719bdb80b
> 
> getentropy was added in glibc 2.25
> https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;h=ec15dde7613306cfa574149f61ea38ab3fbba76d;hb=db0242e3023436757bbc7c488a779e6e3343db04#l116
> 
> causing a build error with bootlin-aarch64-glibc-old which is based on
> glibc 2.24. I found no way to disable freeswitch for this toolchain.

The logical way would be to add a configure.ac test checking for the
availability of getentropy(), and not use it if not available. But
upstream might complain that glibc 2.25 is already quite old and that
it doesn't make sense to use toolchains that use glibc versions older
than 2.25. In that case, we could essentially update a bit our
bootlin-aarch64-glibc-old toolchain to something slightly more recent.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-20 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 20:24 [Buildroot] [PATCH 1/2] package/thrift: Fix build with LibreSSL and OpenSSL 4.x Bernd Kuhls
2026-09-12 20:24 ` [Buildroot] [PATCH 2/2] package/libressl: security bump version to 4.3.2 Bernd Kuhls
2026-10-20 20:59   ` Thomas Petazzoni via buildroot [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=atfV3uwCqo4u7Hhq@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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