From: Florian Weimer <fweimer@redhat.com>
To: amb via Libc-help <libc-help@sourceware.org>
Cc: amb <aaronrmb@gmail.com>
Subject: Re: [Bug libc/23323] Recommendations for devs stuck with old glibc versions
Date: Thu, 30 Nov 2023 12:58:35 +0100 [thread overview]
Message-ID: <87h6l3v4es.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAAJF+LkoAQZWiGZ0xDfGRE0xMYVDxM5vCN1Oofz89m9r4Xoc2g@mail.gmail.com> (amb via Libc-help's message of "Thu, 30 Nov 2023 04:49:18 -0500")
* amb via Libc-help:
> I am forced to build against an old glibc version in order to run my
> code on a large number of target linux systems. For developers like
> me, what is the recommended way to mitigate the issue described in
> https://sourceware.org/bugzilla/show_bug.cgi?id=23323 ?
It's just a missed hardening opportunity. Your binary will likely have
other gadgets in it anyway. Note that we have not treated it as a
security vulnerability.
If your main program does not use ELF constructors, you can use custom
startup files without the ELF constructor trampoline.
Thanks,
Florian
prev parent reply other threads:[~2023-11-30 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 9:49 amb
2023-11-30 11:58 ` Florian Weimer [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=87h6l3v4es.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=aaronrmb@gmail.com \
--cc=libc-help@sourceware.org \
/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 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 read-only IMAP folder(s) and NNTP newsgroup(s).