#glibc

butterflyofChick ⏚ꝃ⌁⁂First I noticed if this « ğ ». Which is : latin small letter g with breve Unicode : U+011F Graph : <a href="https://graphemica.com/%C4%9F" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://graphemica.com/%C4%9F</a>In <a href="https://mstdn.fr/tags/Kabyle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kabyle</a> the correct one is : « ǧ » Which is : latin small letter g with caron Unicode : U+01E7 Graph : <a href="https://graphemica.com/%C7%A7" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://graphemica.com/%C7%A7</a>In this case, ǧ according to <a href="https://mstdn.fr/tags/CLDR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLDR</a> is correct : <a href="https://www.unicode.org/cldr/charts/47/summary/kab.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.unicode.org/cldr/charts/47/summary/kab.html</a>2/…<a href="https://mstdn.fr/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>

butterflyofChick ⏚ꝃ⌁⁂I was reading this part of kab_DZ collate on glibc and something is not correct :Link glibc 2.41-6 : <a href="https://sources.debian.org/src/glibc/2.41-6/localedata/locales/kab_DZ/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sources.debian.org/src/glibc/2.41-6/localedata/locales/kab_DZ/</a>1/…<a href="https://mstdn.fr/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://mstdn.fr/tags/Kabyle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kabyle</a>

BoudThe <a href="https://framapiaf.org/tags/Maneage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Maneage</a> <a href="https://framapiaf.org/tags/reproducibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reproducibility</a> system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the <a href="https://framapiaf.org/tags/GNUCLibrary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUCLibrary</a> = <a href="https://framapiaf.org/tags/GLibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GLibC</a> . We have a draft implementation building glibc *after* <a href="https://framapiaf.org/tags/GCC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GCC</a> [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].Should GLibC be built first? Why (or why not)?[1] <a href="https://savannah.nongnu.org/task/?15390" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://savannah.nongnu.org/task/?15390</a> [2] <a href="https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718</a>

Gardiner BryantThe glibc disaster, Wayland HDR update, and more Linux Gaming News! <a href="https://subscribeto.me/videos/watch/ab8c04fe-8247-4844-88eb-4af189b21c42" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://subscribeto.me/videos/watch/ab8c04fe-8247-4844-88eb-4af189b21c42</a>

mgorny-nyan (he) :autism:🙀🚂🐧If you were ever wondering how fast `<a href="https://social.treehouse.systems/tags/packaging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#packaging</a>.tags.sys_tags()` are growing on GNU / <a href="https://social.treehouse.systems/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>, I have a formula for you (unless I screwed up the maths). For <a href="https://social.treehouse.systems/tags/CPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPython</a> 3.x on <a href="https://social.treehouse.systems/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> 2.y, the total number of tags is:2xy + x + 3y + 3Or equivalently:x(2y + 1) + 3y + 3 y(2x + 3) + x + 3So all other things equal, every new minor version of <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> introduces (2y + 1) tags, and every new minor version of glibc introduces (2x + 3) tags. For glibc 2.41, this means 83 new tags per CPython version. For CPython 3.13, this means 29 new tags per glibc version.Oh, and for a good measure: CPython 3.13 on x86_64 with glibc 2.41 features 1205 compatible wheel tags.

Liam @ GamingOnLinux 🐧🎮The glibc 2.41 update has been causing problems for Linux gaming <a href="https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/</a><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://mastodon.social/tags/LinuxGaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxGaming</a>

boredsquirrel<a href="https://social.heise.de/@ktn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ktn</a> <a href="https://social.heise.de/@ct_Magazin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ct_Magazin</a> <a href="https://social.heise.de/@heiseonline" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@heiseonline</a> <a href="https://techhub.social/@jolla" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jolla</a> <a href="https://tux.social/tags/DesktopLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DesktopLinux</a> fehlt einfach das Geld für bezahlte Sicherheitsexperten, die ernsthaft viel daran arbeiten.<a href="https://tux.social/tags/Wayland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wayland</a> und <a href="https://tux.social/tags/Pipewire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pipewire</a> haben anders als <a href="https://tux.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> keine critical mass, um <a href="https://tux.social/tags/Apps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apps</a> zu diktieren, an welche Regeln sie sich halten müssen. Und Absprachen (<a href="https://tux.social/tags/waylandprotocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#waylandprotocols</a>) sind auch mehr als chaotisch.<a href="https://tux.social/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> vs. <a href="https://tux.social/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a>, <a href="https://tux.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> vs. <a href="https://tux.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a>, es gibt irgendwie keinen Konsens für <a href="https://tux.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>

Thorsten Leemhuis (acct. 1/4)Linus on different levels for the <a href="https://fosstodon.org/tags/x86_64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#x86_64</a> architecture:<a href="https://lore.kernel.org/all/CAHk-%3Dwh_b8b1qZF8_obMKpF%2BxfYnPZ6t38F1%2B5pK-eXNyCdJ7g@mail.gmail.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lore.kernel.org/all/CAHk-%3Dwh_b8b1qZF8_obMKpF%2BxfYnPZ6t38F1%2B5pK-eXNyCdJ7g@mail.gmail.com/</a>'"[…] The whole "v2", "v3", "v4" etc naming seems to be some crazy <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> artifact and is stupid and needs to die.It has no relevance to anything. Please do *not* introduce that mind-fart into the <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel</a> sources.[…] it's entirely unofficial, and it's a completely broken model.There is a very real model for microarchitectural features, and it's the CPUID bits. […]'" <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxKernel</a>

zirias (on snac)Having my <code>$HOME</code> on <a href="https://snac.bsd.cafe?t=nfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NFS</a>, I'm sometimes annoyed by lots of applications "freezing" when there's some issue with the NFS server. I just decided I'll try to prevent this in <a href="https://snac.bsd.cafe?t=xmoji" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xmoji</a>. Now, how to do that? Nonblocking mode (which I use for sockets etc) doesn't do anything for regular files, they're always "ready to read/write". Still, actually reading or writing might block your thread. Then there's <a href="https://snac.bsd.cafe?t=posix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> <a href="https://snac.bsd.cafe?t=aio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aio</a>. From what I found, this has issues in real implementations, e.g. <a href="https://snac.bsd.cafe?t=freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> uses kernel workers for implementing it, which are limited, and also doesn't even allow it on NFS by default, because it could cause deadlocks. Looking at the <a href="https://snac.bsd.cafe?t=linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> side, there seems to be some platform-specific async I/O implementation in the kernel, but <a href="https://snac.bsd.cafe?t=glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> implements the POSIX aio entirely in userspace... 🤯 Ok, screw all that. I'll do the simple thing and use worker <a href="https://snac.bsd.cafe?t=threads" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#threads</a> for file I/O calls, should be somewhat easy as I already have a "threadpool" in <a href="https://snac.bsd.cafe?t=poser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poser</a>. I just started doing that in my "filewatcher" in case it needs to use <code>stat()</code>: <a href="https://github.com/Zirias/xmoji/commit/8ba637c482e82791c9e20db21ce95a3e854b6f86" rel="nofollow noopener noreferrer" target="_blank">https://github.com/Zirias/xmoji/commit/8ba637c482e82791c9e20db21ce95a3e854b6f86</a> More to follow ... 😉 <a href="https://snac.bsd.cafe?t=c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://snac.bsd.cafe?t=development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://snac.bsd.cafe?t=async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a>

MiraiI have a question related to distributing games on Linux. I'm making a game from scratch with C and the help of some libraries like SDL2 and Libconfig. I've heard that making "portable" programs is quite difficult on Linux due to Glibc and other things related to libraries. How true is this, and what can I do to work around it? Any information is appreciated. (Next post) <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mstdn.social/tags/GameDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GameDev</a> <a href="https://mstdn.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://mstdn.social/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://mstdn.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> <a href="https://mstdn.social/tags/Coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coding</a> <a href="https://mstdn.social/tags/Help" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Help</a>

Alien BOBSlackware-current has absorbed my multilib gcc and glibc packagesEver since the birth of 64-bit Slackware in 2009, I have been maintaining a multilib repository. Today, 15 years later, things are changing!You may know it or not, depending on your age, but I have created 64-bit Slackware from scratch late 2008 and early 2009 as a project <a href="https://alien.slackbook.org/blog/slackware-current-has-absorbed-my-multilib-gcc-and-glibc-packages/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://alien.slackbook.org/blog/slackware-current-has-absorbed-my-multilib-gcc-and-glibc-packages/</a><a href="https://fosstodon.org/tags/Slackware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Slackware</a> <a href="https://fosstodon.org/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://fosstodon.org/tags/compat32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compat32</a> <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/multilib" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multilib</a>

Christos Argyropoulos MD, PhDFun project: a <a href="https://mstdn.science/tags/memory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#memory</a> manager for multi-lang applications (<a href="https://mstdn.science/tags/c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#c</a>, <a href="https://mstdn.science/tags/cplusplus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cplusplus</a> <a href="https://mstdn.science/tags/assembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assembly</a> <a href="https://mstdn.science/tags/fortran" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fortran</a>) in which workflow management is done by <a href="https://mstdn.science/tags/Perl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Perl</a>. Currently allocates using either <a href="https://mstdn.science/tags/perl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#perl</a> strings or <a href="https://mstdn.science/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> malloc/calloc. Other allocators <a href="https://mstdn.science/tags/jemalloc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jemalloc</a> coming soon. <a href="https://github.com/chrisarg/task-memmanager" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/chrisarg/task-memmanager</a>

Neustradamus :xmpp: :linux:<a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> 2.40 has been released (<a href="https://mastodon.social/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> / <a href="https://mastodon.social/tags/GNUC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUC</a> / <a href="https://mastodon.social/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> / <a href="https://mastodon.social/tags/LIBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LIBC</a>) <a href="https://gnu.org/software/libc/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gnu.org/software/libc/</a>

Tomášsummer<a href="https://merveilles.town/tags/unix_surrealism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix_surrealism</a> <a href="https://merveilles.town/tags/technomage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#technomage</a> <a href="https://merveilles.town/tags/comic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#comic</a> <a href="https://merveilles.town/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://merveilles.town/tags/summer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#summer</a> <a href="https://merveilles.town/tags/fediart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediart</a> <a href="https://merveilles.town/tags/monochrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#monochrome</a> <a href="https://merveilles.town/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://merveilles.town/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://merveilles.town/tags/runbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#runbsd</a>

83r71nA recent discovery has highlighted a serious vulnerability affecting at least 700,000 OpenSSH servers globally. This vulnerability, named "regreSSHion," allows attackers to execute code remotely with root privileges on glibc-based Linux systems. The flaw, identified as CVE-2024-6387, is described as critical and stems from a signal handler race condition within OpenSSH's server. If exploited, this vulnerability could lead to complete system takeover. It's important to note that this vulnerability is a regression of a previously patched issue (CVE-2006-5051) and impacts OpenSSH versions 8.5p1 through 9.7p1. <a href="https://www.openssh.com/releasenotes.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.openssh.com/releasenotes.html</a><a href="https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt</a><a href="https://ioc.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://ioc.exchange/tags/openssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> <a href="https://ioc.exchange/tags/server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#server</a> <a href="https://ioc.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerability</a> <a href="https://ioc.exchange/tags/regresshion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#regresshion</a> <a href="https://ioc.exchange/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://ioc.exchange/tags/cve" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cve</a> <a href="https://ioc.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://ioc.exchange/tags/update" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#update</a> <a href="https://ioc.exchange/tags/qualys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qualys</a>

Some Bits: Nelson's Linkblogpollyfill-glibc: Hackery to let new binaries run on old Linux systems. The docs directory has a bunch of interesting technical info on linker tricks <a href="https://github.com/corsix/polyfill-glibc/tree/main" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/corsix/polyfill-glibc/tree/main</a> <a href="https://tech.lgbt/tags/compatibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compatibility</a> <a href="https://tech.lgbt/tags/via" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#via</a>:lobsters <a href="https://tech.lgbt/tags/pollyfill" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pollyfill</a> <a href="https://tech.lgbt/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://tech.lgbt/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://tech.lgbt/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hack</a> <a href="https://tech.lgbt/tags/libc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libc</a> #+

FellI just learnt about `jemalloc` in order to fix the memory hunger of Synapse.So yeah, Python developers will rather hijack the glibc memory allocator than switch to a resource efficient language.<a href="https://ma.fellr.net/tags/jemalloc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jemalloc</a> <a href="https://ma.fellr.net/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> <a href="https://ma.fellr.net/tags/Synapse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Synapse</a> <a href="https://ma.fellr.net/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://ma.fellr.net/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://ma.fellr.net/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a>

matthew - retroedge.techQuestion on the PHP glibc vulnerability: Does anyone know a blog post or other documentation for how to turn off the character set that allows the vulnerability in Ubuntu and Debian? Here's a good blog post by Rocky Linux on the subject, but I'm not sure how to translate the instructions to Debian and Ubuntu. <a href="https://rockylinux.org/pt_BR/news/glibc-vulnerability-april-2024/?language=en" rel="nofollow noopener noreferrer" target="_blank">https://rockylinux.org/pt_BR/news/glibc-vulnerability-april-2024/?language=en</a> <a class="hashtag" href="https://social.retroedge.tech/tag/sysadmin" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a class="hashtag" href="https://social.retroedge.tech/tag/security" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a class="hashtag" href="https://social.retroedge.tech/tag/php" rel="nofollow noopener noreferrer" target="_blank">#php</a> <a class="hashtag" href="https://social.retroedge.tech/tag/glibc" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a class="hashtag" href="https://social.retroedge.tech/tag/debian" rel="nofollow noopener noreferrer" target="_blank">#debian</a> <a class="hashtag" href="https://social.retroedge.tech/tag/ubuntu" rel="nofollow noopener noreferrer" target="_blank">#ubuntu</a> <a class="hashtag" href="https://social.retroedge.tech/tag/rockylinux" rel="nofollow noopener noreferrer" target="_blank">#rockylinux</a> <a class="hashtag" href="https://social.retroedge.tech/tag/linux" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

mart-wAs fixes for the current <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/php" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#php</a> <a href="https://chaos.social/tags/vulnerability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerability</a> are not reliably available yet, keep in mind that a workaround exists for those of you who don’t need support for the ISO-2022-CN-EXT character set: <a href="https://rockylinux.org/news/glibc-vulnerability-april-2024/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://rockylinux.org/news/glibc-vulnerability-april-2024/</a>This should be quite straightforward to apply on most machines – except those running <a href="https://chaos.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a>. If you do use NixOS, my solution might help you bridge the gap until the proper fix is upstream: <a href="https://git.brokentech.cloud/mart-w/nixos-workaround-cve-2024-2961" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://git.brokentech.cloud/mart-w/nixos-workaround-cve-2024-2961</a>Thanks <a href="https://chaos.social/@hexa" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hexa</a> for pointing me in the right direction!

Phil Baker :fedora: :freebsd:I just applied this workaround to my two <a href="https://fosstodon.org/tags/AlmaLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AlmaLinux</a> servers <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://rockylinux.org/news/glibc-vulnerability-april-2024/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://rockylinux.org/news/glibc-vulnerability-april-2024/</a>

Recent searches

Search options

Administered by:

Server stats: