mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Arjun Shankar <arjun@redhat.com>
Cc: musl@lists.openwall.com, Florian Weimer <fweimer@redhat.com>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: [musl] Plans to remove nscd in Fedora
Date: Mon, 19 Oct 2020 21:08:56 -0400	[thread overview]
Message-ID: <20201020010855.GE17637@brightrain.aerifal.cx> (raw)
In-Reply-To: <805098991.18032044.1603106011330.JavaMail.zimbra@redhat.com>

On Mon, Oct 19, 2020 at 07:13:31AM -0400, Arjun Shankar wrote:
> Hi all,
> 
> I am one of the maintainers for glibc in Fedora. We are planning to remove
> nscd from Fedora in the near future, targeting the Fedora 34 release [1].
> 
> Florian recently pointed out to me that this can impact users of musl-libc
> binaries since musl is nscd-aware.
> 
> I can see that the Fedora musl-libc package has no "official" dependent
> packages (excepting musl-devel) in the Fedora repositories, but I expect
> that there might be packages/applications from out of the distribution and
> use cases that are affected by or possibly break with the removal of nscd.
> 
> I'm writing to get some clarity on this.
> 
> Best Regards,
> Arjun
> 
> [1] WIP: https://fedoraproject.org/wiki/Changes/RemoveNSCD

The only capacity in which musl uses nscd is to access custom
user/group backends provided through it. 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.

Rich

  reply	other threads:[~2020-10-20  1:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1924902939.18027073.1603105167534.JavaMail.zimbra@redhat.com>
2020-10-19 11:13 ` Arjun Shankar
2020-10-20  1:08   ` Rich Felker [this message]
2020-10-23 11:35     ` Florian Weimer
2020-10-23 12:01       ` Tim Tassonis
2020-10-23 12:09         ` Florian Weimer
2020-10-23 13:29     ` Carlos O'Donell
2020-10-23 13:37       ` Laurent Bercot
2020-10-23 14:14       ` Jesse Hathaway
2020-10-23 16:58         ` Rich Felker
2020-10-26 12:20         ` Florian Weimer
2020-10-26 13:12           ` Rich Felker
2020-11-02 13:54             ` Florian Weimer
2020-11-02 14:50               ` Rich Felker
2020-11-03  9:07                 ` Florian Weimer
2020-11-03 15:41                   ` Rich Felker

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=20201020010855.GE17637@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=arjun@redhat.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).