From: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: fweimer@redhat.com, ludo@gnu.org, libc-alpha@sourceware.org,
ashankar@redhat.com
Subject: Re: On the removal of nscd from Fedora, and the future of nscd.
Date: Mon, 28 Feb 2022 20:02:37 -0500 [thread overview]
Message-ID: <xnv8wy7adu.fsf@greed.delorie.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2202282305270.2276807@digraph.polyomino.org.uk> (message from Joseph Myers on Mon, 28 Feb 2022 23:09:27 +0000)
Joseph Myers <joseph@codesourcery.com> writes:
> I think there is a reasonable case that all NSS modules that aren't in
> libc (especially those not shipped with glibc) should be loaded only in a
> separate process, not in the main process doing the name lookup, to avoid
> issues with name lookup loading more or less arbitrary libraries into the
> process doing the lookup.
Hmm... I hadn't thought of it that way, but the security implications
are compelling... and we don't hardcode the search path either, so the
user can override it via environment (unless setuid), I think.
{
char *shlib_name;
if (__asprintf (&shlib_name, "libnss_%s.so%s",
module->name, __nss_shlib_revision) < 0)
/* This is definitely a temporary failure. Do not update
module->state. This will trigger another attempt at the next
call. */
return false;
handle = __libc_dlopen (shlib_name);
free (shlib_name);
}
next prev parent reply other threads:[~2022-03-01 1:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:55 On the removal of nscd from Fedora, and the future of nscd Carlos O'Donell via Libc-alpha
2022-02-28 23:02 ` DJ Delorie via Libc-alpha
2022-02-28 23:09 ` Joseph Myers
2022-03-01 1:02 ` DJ Delorie via Libc-alpha [this message]
2022-03-01 9:10 ` Ludovic Courtès via Libc-alpha
2022-03-01 16:54 ` DJ Delorie via Libc-alpha
2022-03-01 17:44 ` Ludovic Courtès via Libc-alpha
2022-03-01 18:31 ` DJ Delorie via Libc-alpha
2022-03-03 13:40 ` Ludovic Courtès via Libc-alpha
2022-03-06 22:05 ` John Ericson
2022-11-20 18:34 ` Florian Klink
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xnv8wy7adu.fsf@greed.delorie.com \
--to=libc-alpha@sourceware.org \
--cc=ashankar@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=ludo@gnu.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).