[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 23 Oct 2020 13:35:56 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Rich Felker <dalias@...c.org>
Cc: Arjun Shankar <arjun@...hat.com>, musl@...ts.openwall.com, Carlos
O'Donell <carlos@...hat.com>
Subject: Re: Plans to remove nscd in Fedora
* Rich Felker:
> The only capacity in which musl uses nscd is to access custom
> user/group backends provided through it.
And that's the only way to get this data into musl programs.
> musl specifically does not use nss itself because it's not compatible
> with static linking and because loading arbitrary module libraries
> into the calling process's core is not safe and goes against best
> practices. I believe the glibc folks were starting to realize this
> too, so it was kinda my hope that nscd would become the main/only way
> nss modules are accessed on glibc too.
This requirement has largely been pushed into the NSS modules
themselves. If they do more than just opening a files or sockets, they
need to offload part of the functionality (actually most of it) into a
separate daemon. This is the difference between nss_ldap and nss_ldapd.
SSSD has largely assumed this role for the non-hosts maps. It looks
like that systemd-resolved will cover the hosts maps. So it's unclear
what's left for nscd to handle.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
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.
