#glibc

3 post2 partecipanti0 post oggi

jbzmusl libc - Functional differences from glibc ｢ ISO C and POSIX require the end-of-file status for a FILE to be sticky, i.e. for it to preclude further reads once it’s set, unless it’s explicitly cleared. musl has always honored this requirement. glibc versions prior to 2.28 ignored it and always returned new input, if available, even after the EOF flag is set ｣<a href="https://wiki.musl-libc.org/functional-differences-from-glibc.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://wiki.musl-libc.org/functional-differences-from-glibc.html</a><a href="https://indieweb.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a> <a href="https://indieweb.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://indieweb.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://indieweb.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

jbz⚠️ Steam Will Stop Working on Outdated Linux Systems This August | Linuxiac ｢ According to a recent announcement, the Steam client will no longer run on any distribution with a GNU C Library (glibc) version older than 2.31 starting August 15, 2025.Users who stay on an outdated toolchain will find not only Steam but also any purchased games unable to launch until the underlying operating system is upgraded ｣<a href="https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxiac.com/steam-will-stop-working-on-outdated-linux-systems-this-august/</a><a href="https://indieweb.social/tags/steam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#steam</a> <a href="https://indieweb.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://indieweb.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://indieweb.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

Vitexglibc (2.41-7) unstable; urgency=medium Starting with glibc 2.41, shared libraries requiring an executable stack cannot be dynamically loaded through the <a href="https://f.cz/tags/dlopen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dlopen</a> mechanism from a binary that does not require an executable stack. This change aims to improve security, as the previous behavior was used as a vector for RCE (<a href="https://f.cz/tags/CVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CVE</a>-2023-38408). Attempting to do so will result in the following error: cannot enable executable stack as shared object requires: Invalid argument While most libraries generated in the past 20 years do not require an executable stack, some third-party software still need this capability. Many vendors have already updated their binaries to address this. If you need to run a program that requires an executable stack through dynamic loaded shared libraries, you can use the glibc.rtld.execstack tunable: Glibc6_TUNABLES=glibc.rtld.execstack=2 ./program -- Aurelien Jarno <aurel32@debian.org> Sun, 13 Apr 2025 14:41:11 +0200<a href="https://f.cz/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://f.cz/tags/Changelog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Changelog</a> <a href="https://f.cz/tags/GLibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GLibC</a> <a href="https://f.cz/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://f.cz/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

SourcewareSourceware Survey 2025 ResultsIn the end we got 103 (!) responses with a nice mix of developers, users and maintainers from various hosted projects.<a href="https://sourceware.org/survey-2025" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sourceware.org/survey-2025</a><a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/cygwin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cygwin</a> <a href="https://fosstodon.org/tags/dwarfstd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dwarfstd</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elfutils</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/gdb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gdb</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/libabigail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/systemTap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemTap</a> <a href="https://fosstodon.org/tags/valgrind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valgrind</a> <a href="https://fosstodon.org/tags/bzip2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bzip2</a> <a href="https://fosstodon.org/tags/libffi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libffi</a> <a href="https://fosstodon.org/tags/dwz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dwz</a> <a href="https://fosstodon.org/tags/debugedit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugedit</a> <a href="https://fosstodon.org/tags/gnupoke" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnupoke</a> <a href="https://fosstodon.org/tags/bunsen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bunsen</a> <a href="https://fosstodon.org/tags/lvm2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lvm2</a> <a href="https://fosstodon.org/tags/annobin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#annobin</a> <a href="https://fosstodon.org/tags/gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnu</a>-gabi <a href="https://fosstodon.org/tags/cgen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cgen</a> <a href="https://fosstodon.org/tags/kawa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kawa</a> <a href="https://fosstodon.org/tags/insight" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#insight</a> <a href="https://fosstodon.org/tags/pacme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pacme</a>

stateful being<a href="https://mastodon.social/tags/tek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tek</a> 0.2.0 out now: <a href="https://codeberg.org/unspeaker/tek/releases/tag/0.2.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/unspeaker/tek/releases/tag/0.2.0</a>it's buggy as hell, and about half the features i've showcased previously are disabled for now. but, more importantly, i've managed to build it as a single binary that you should be able to run on any <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> with <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> and <a href="https://mastodon.social/tags/jack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jack</a>... let me know what happens!<a href="https://mastodon.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://mastodon.social/tags/tui" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tui</a> <a href="https://mastodon.social/tags/daw" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#daw</a>

Felix Palmen :freebsd: :c64:Today, I implemented the <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#await</a> pattern (as known from <a href="https://mastodon.bsd.cafe/tags/csharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csharp</a> and meanwhile quite some other languages) ...... in good old <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a>! 😎 Well, at least sort of.* It requires some standard library support, namely <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a> user context switching with <a href="https://mastodon.bsd.cafe/tags/getcontext" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getcontext</a> and friends, which was deprecated in POSIX-1.2008. But it's still available on many systems, including <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (with <a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>). It's NOT available e.g. on <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a>, or Linux with some alternative libc.* I can't do anything about the basic language syntax, so some boilerplate comes with using it.* It has some overhead (room for extra stacks, even extra syscalls as getcontext unfortunately also always saves/restores the signal mask)But then ... async/await in C! 🥳 Here are the docs: <a href="https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html</a><a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

Felix Palmen :freebsd: :c64:I finally eliminated the need for a dedicated <a href="https://mastodon.bsd.cafe/tags/thread" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thread</a> controlling the pam helper <a href="https://mastodon.bsd.cafe/tags/process" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#process</a> in <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swad</a>. 🥳 The building block that was still missing from <a href="https://mastodon.bsd.cafe/tags/poser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#poser</a> was a way to await some async I/O task performed on the main thread from a worker thread. So I added a class to allow exactly that. The naive implementation just signals the main thread to carry out the requested task and then waits on a <a href="https://mastodon.bsd.cafe/tags/semaphore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#semaphore</a> for completion, which of course blocks the worker thread.Turns out we can actually do better, reaching similar functionality like e.g. <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#async</a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#await</a> in C#: Release the worker thread to do other jobs while waiting. The key to this is user context switching support like offered by <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#POSIX</a>-1.2001 <a href="https://mastodon.bsd.cafe/tags/getcontext" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#getcontext</a> and friends. Unfortunately it was deprecated in POSIX-1.2008 without an obvious replacement (the docs basically say "use threads", which doesn't work for my scenario), but still lots of systems provide it, e.g. <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetBSD</a>, <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> (with <a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a>) ...The posercore lib now offers both implementations, prefering to use user context switching if available. It comes at a price: Every thread job now needs its private stack space (I allocated 64kiB there for now), and of course the switching takes some time as well, but that's very likely better than leaving a task idle waiting. And there's a restriction, resuming must still happen on the same thread that called the "await", so if this thread is currently busy, we have to wait a little bit longer. I still think it's a very nice solution. 😎 In any case, the code for the PAM credential checker module looks much cleaner now (the await "magic" happens on line 174): <a href="https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c</a><a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>

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>

C++NowC++Now 2025 SESSION ANNOUNCEMENT: Using TLA+ to Fix a Very Difficult glibc Bug by Malte Skarupke<a href="https://schedule.cppnow.org/session/2025/using-tla-to-fix-a-very-difficult-glibc-bug/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://schedule.cppnow.org/session/2025/using-tla-to-fix-a-very-difficult-glibc-bug/</a>Register now at <a href="https://cppnow.org/registration/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cppnow.org/registration/</a><a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> <a href="https://mastodon.social/tags/cplusplus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cplusplus</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/TLA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLA</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>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> are something different...</li></ul>

Christian Brauner 🦊🐺Who at <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> do we need to bribe to get <a href="https://fosstodon.org/@codonell" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@codonell</a> :"I think we really need to expose some sort of clone/clone3 wrapper, with some guardrails against unsupportable scenarios (such as spawning new threads in the current process)."finally implemented! It really is missing! <a href="https://patchwork.sourceware.org/project/glibc/patch/20230803163558.991832-7-adhemerval.zanella@linaro.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://patchwork.sourceware.org/project/glibc/patch/20230803163558.991832-7-adhemerval.zanella@linaro.org</a>

unixbhaskarUmmm 🤔<a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> <a href="https://mastodon.social/tags/libc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libc</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://mastodon.social/tags/binary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#binary</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://jangafx.com/insights/linux-binary-compatibility" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://jangafx.com/insights/linux-binary-compatibility</a>

Kevin Karhan :verified:<a href="https://kitsunes.club/@Jessica" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Jessica</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> +9001%The reason I don't use <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GlibC</a> on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> is because it's <a href="https://infosec.space/@kkarhan/114175034719920644" rel="nofollow noopener noreferrer" target="_blank">constantly breaking userspace</a>…

Несерьёзный ВыдумщикПерестал работать <a class="hashtag" href="https://idealists.su/tag/portal2" rel="nofollow noopener noreferrer" target="_blank">#Portal2</a> или что-то другое из игрушек на обновившемся <a class="hashtag" href="https://idealists.su/tag/linux" rel="nofollow noopener noreferrer" target="_blank">#linux</a> ? При запуске в терминале пишет:<pre><code>failed to dlopen <a href="http://engine.so" rel="nofollow noopener noreferrer" target="_blank">engine.so</a> error=engine.so: cannot enable executable stack as shared object requires: Invalid argument ... AppFramework : Unable to load module <a href="http://engine.so" rel="nofollow noopener noreferrer" target="_blank">engine.so</a>! </code></pre>Почти наверняка это из-за того, что изменилась версия <a class="hashtag" href="https://idealists.su/tag/glibc" rel="nofollow noopener noreferrer" target="_blank">#glibc</a><pre><code>/usr/lib/libc.so.6 GNU C Library (GNU libc) stable release version 2.41. </code></pre>И вот раз так — раз оно уже 2.41, тогда можно спокойно пропатчить два бинарника:<pre><code>patchelf --clear-execstack /path/to/Portal2/game/bin/linux32/engine.so patchelf --clear-execstack /path/to/Portal2/game/bin/linux32/valve_avi.so </code></pre>Всё, будет работать как и раньше :)<a class="hashtag" href="https://idealists.su/tag/linuxgaming" rel="nofollow noopener noreferrer" target="_blank">#LinuxGaming</a> <a class="hashtag" href="https://idealists.su/tag/игры" rel="nofollow noopener noreferrer" target="_blank">#игры</a> <a class="hashtag" href="https://idealists.su/tag/games" rel="nofollow noopener noreferrer" target="_blank">#games</a> <a class="u-url mention" href="https://mastodon.social/@russian_mastodon" rel="nofollow noopener noreferrer" target="_blank">@russian_mastodon</a> <a class="u-url mention" href="https://lor.sh/@ru" rel="nofollow noopener noreferrer" target="_blank">@ru</a> <a class="u-url mention" href="https://3zi.ru/@Russia" rel="nofollow noopener noreferrer" target="_blank">@Russia</a>

Douglas J HunleyTuning the <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#glibc</a> memory allocator (for <a href="https://fosstodon.org/tags/Postgres" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Postgres</a>) <a href="https://vondra.me/posts/tuning-the-glibc-allocator-for-postgres/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vondra.me/posts/tuning-the-glibc-allocator-for-postgres/</a>

NerdNextDoor :Blobhaj:Making 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/Distro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Distro</a> from the <a href="https://mastodon.social/tags/LFN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LFN</a> guide by MapleCircuit. (Great guy, search up the series <a href="https://mastodon.social/tags/LinuxfromNothing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxfromNothing</a> and go follow him!!!)I’m using <a href="https://mastodon.social/tags/Musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Musl</a> instead of <a href="https://mastodon.social/tags/Glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Glibc</a> for funsies.I’m <a href="https://mastodon.social/tags/Nerdy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nerdy</a> as shit, and that’s pretty cool.<a href="https://mastodon.social/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a> <a href="https://mastodon.social/tags/Technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Technology</a> <a href="https://mastodon.social/tags/Nerd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nerd</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>

hubertfOn thread vs. process permissionsIn common Unix and POSIX systems, all threads in a process are supposed to have the same permission. So why does the vortex8 program work as exploited, where one thread sets different permissions than another one using setresuid/setresgid?Reference: <a href="https://man7.org/linux/man-pages/man2/setresuid.2.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://man7.org/linux/man-pages/man2/setresuid.2.html</a>Answer in thread.<a href="https://mastodon.social/tags/ctf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ctf</a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://mastodon.social/tags/posix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#posix</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/syscall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#syscall</a> <a href="https://mastodon.social/tags/overthewire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#overthewire</a> <a href="https://mastodon.social/tags/vortex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vortex</a>

Ricerche recenti

Opzioni di ricerca

Amministrato da:

Statistiche del server: