From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/expat: fix no high quality entropy warning on Linux <3.17 or glibc <2.25
Date: Fri, 4 Sep 2026 14:18:41 +0200 [thread overview]
Message-ID: <20260904121841.405853-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260825093406.1932342-1-thomas.devoogdt@barco.com>
In reply of:
> xmlparse.c:150:4: error: #error You do not have support for any sources of high quality entropy enabled.
> For end user security, that is probably not what you want. Your options include:
> * Linux >=3.17 + glibc >=2.25 (getrandom): HAVE_GETRANDOM,
> * Linux >=3.17 + glibc (including <2.25) (syscall SYS_getrandom): HAVE_SYSCALL_GETRANDOM,
> * BSD / macOS >=10.7 / glibc >=2.36 (arc4random_buf): HAVE_ARC4RANDOM_BUF,
> * BSD / macOS (including <10.7) / glibc >=2.36 (arc4random): HAVE_ARC4RANDOM,
> * BSD / macOS >=10.12 / glibc >=2.25 (getentropy): HAVE_GETENTROPY,
> * Linux (including <3.17) / BSD / macOS (including <10.7) / Solaris >=8 (/dev/urandom): XML_DEV_URANDOM,
> * Windows >=Vista (rand_s): _WIN32.
> If you insist on not using any of these, bypass this error by defining XML_POOR_ENTROPY and be vulnerable to hash flooding;
> you have been warned. If you have reasons to patch this detection code away or need changes to the build system, please open a bug. Thank you!
>
> This is caused by the upstream commit "Autotools: Stop using /dev/urandom by default"
> https://github.com/libexpat/libexpat/commit/d30eca113a44562137d59835cf2255ea32d11ba6
>
> But since all Linux systems have /dev/urandom, we can just enable it by default.
>
> Moved config options to multiline layout to fit within the 80 characters.
>
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Applied to 2025.02.x & 2026.05.x. Thanks
> ---
> package/expat/expat.mk | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/package/expat/expat.mk b/package/expat/expat.mk
> index 7645edfd52..a82be75a4d 100644
> --- a/package/expat/expat.mk
> +++ b/package/expat/expat.mk
> @@ -14,8 +14,16 @@ EXPAT_CPE_ID_VENDOR = libexpat_project
> EXPAT_CPE_ID_PRODUCT = libexpat
>
> EXPAT_CONF_OPTS = \
> - --without-docbook --without-examples --without-tests --without-xmlwf
> -HOST_EXPAT_CONF_OPTS = --without-docbook --without-examples --without-tests
> + --with-dev-urandom \
> + --without-docbook \
> + --without-examples \
> + --without-tests \
> + --without-xmlwf
> +
> +HOST_EXPAT_CONF_OPTS = \
> + --without-docbook \
> + --without-examples \
> + --without-tests
>
> $(eval $(autotools-package))
> $(eval $(host-autotools-package))
> --
> 2.43.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-04 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 9:34 [Buildroot] [PATCH] package/expat: fix no high quality entropy warning on Linux <3.17 or glibc <2.25 Thomas Devoogdt
2026-08-25 20:10 ` Julien Olivain via buildroot
2026-09-04 12:18 ` Thomas Perale 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=20260904121841.405853-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=thomas@devoogdt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.