* libevent changes ABI on >=glibc-2.36 upgrade, breaking e.g. Tor
@ 2023-03-15 4:20 Sam James
0 siblings, 0 replies; only message in thread
From: Sam James @ 2023-03-15 4:20 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
libevent hasn't made a release in a while, so this is probably worth
getting out there.
If libevent is built against a libc without arc4random, like
<=glibc-2.36, it'll provide evutil_secure_rng_add_bytes. If
it's built against a libc providing arc4random, it'll stop
providing evutil_secure_rng_add_bytes without changing SONAME.
This breaks consumers like Tor which uses it if it exists in
libevent, leading to runtime issues:
Feb 15 04:57:23 systemd: Starting tor.service...
Feb 15 04:57:23 tor: /usr/bin/tor: symbol lookup error:
/usr/bin/tor: undefined symbol: evutil_secure_rng_add_bytes
This originally bit us in Gentoo  and there's an upstream
bug report  and patch available now (but no new release)
to always provide evutil_secure_rng_add_bytes, but stubbed
out if libc provides arc4random.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-03-15 4:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-15 4:20 libevent changes ABI on >=glibc-2.36 upgrade, breaking e.g. Tor Sam James
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).