[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20261107214934.GH23438@brightrain.aerifal.cx>
Date: Sat, 7 Nov 2026 16:49:34 -0500
From: Rich Felker <dalias@...c.org>
To: "Ammanaghatta Shivakumar, Basavesh" <basavesh.shivakumar@....edu>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>,
"tg@...lvis.org" <tg@...lvis.org>,
"Priya, Swarn" <swarn.priya@....edu>
Subject: Re: explicit-path `dlopen` does not satisfy later `DT_NEEDED`
by SONAME
On Sat, Nov 07, 2026 at 08:23:27AM +0000, Ammanaghatta Shivakumar, Basavesh wrote:
> These tools sit low in the software supply chain, so I’d like to see
> these bugs fixed before someone exploits them.
Our not supporting some particular functionality, outside the scope of
the standards that we purport to support, is not a "bug".
We are not going to be badgered into adopting functionality because
LLM slop uses scary words like "exploit".
If you find actual bugs -- deviations from behavior specified by ISO C
or POSIX, or places where nonstandardized functionality we do
implement differs in ways that seem unintentional from other
implementations, or violations of expected security boundaries, etc.
-- you are welcome to report them with a concise explanation written
by a human being who has examined the issue and has reason to believe
there is a real bug, preferably with a minimal reproducing test case
also written by a human being.
Please do not just send output of the slop extruder. It just instills
distrust and wastes actual people's time trying to figure out if
there's something meaningful to look at or not.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
