From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 24325 invoked from network); 2 Nov 2020 14:50:59 -0000
Received: from mother.openwall.net (195.42.179.200)
  by inbox.vuxu.org with ESMTPUTF8; 2 Nov 2020 14:50:59 -0000
Received: (qmail 19552 invoked by uid 550); 2 Nov 2020 14:50:54 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 18423 invoked from network); 2 Nov 2020 14:50:37 -0000
Date: Mon, 2 Nov 2020 09:50:18 -0500
From: Rich Felker <dalias@libc.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Jesse Hathaway <jesse@mbuki-mvuki.org>, musl@lists.openwall.com,
	Arjun Shankar <arjun@redhat.com>,
	Carlos O'Donell <carlos@redhat.com>
Message-ID: <20201102145017.GS534@brightrain.aerifal.cx>
References: <1924902939.18027073.1603105167534.JavaMail.zimbra@redhat.com>
 <805098991.18032044.1603106011330.JavaMail.zimbra@redhat.com>
 <20201020010855.GE17637@brightrain.aerifal.cx>
 <bfa416c5-8baf-64ba-cdf7-8ebb83dfc26b@redhat.com>
 <CANSNSoXvHSN6fBo6oAdZzC7OFrrekAxSiFCY9XZ-tp5wTCTCJA@mail.gmail.com>
 <874kmhdvqw.fsf@oldenburg2.str.redhat.com>
 <20201026131254.GL534@brightrain.aerifal.cx>
 <87zh3zg8yw.fsf@oldenburg2.str.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87zh3zg8yw.fsf@oldenburg2.str.redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] Plans to remove nscd in Fedora

On Mon, Nov 02, 2020 at 02:54:31PM +0100, Florian Weimer wrote:
> * Rich Felker:
> 
> > It's not mandatory on glibc, but it's a widely deployed existing
> > interface on most "big" systems, and it's easy to add with a quick
> > apt-get or whatever on others if you find you need it for integration
> > with non-glibc binaries.
> 
> This has not been true for quite a few years because using nscd along
> with sssd for the same databases is not supported (sssd is where all the
> domain integration work happens these days):
> 
> <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system-level_authentication_guide/usingnscd-sssd>
> 
> SUSE also recommends disabling parts of nscd:
> 
> | -  Modify  /etc/nscd.conf
> | 
> | enable-cache   passwd    no
> | enable-cache   group      no
> 
> <https://www.suse.com/support/kb/doc/?id=000019039>
> 
> I think SUSE has largely switched to SSSD as well for the most recent
> product releases, but I do not have much insight into their work
> unfortunately.
> 
> > If it remains easy to add, having it not installed by default is
> > really not a big deal,
> 
> (we have been in this situation for many, many years)
> 
> > but I kinda worry about bitrot/breakage from suddenly having far fewer
> > users.
> 
> nscd is already very broken and has issues with workloads that trigger
> many cache misses.

Thanks for filling me in on the status of this. Perhaps
https://github.com/pikhq/musl-nscd (not part of musl, but by a
long-time contributor) would be a useful basis for building a
replacement glibc systems could use too?

Rich