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 4336 invoked from network); 23 Oct 2020 13:37:42 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 23 Oct 2020 13:37:42 -0000 Received: (qmail 18017 invoked by uid 550); 23 Oct 2020 13:37:40 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17990 invoked from network); 23 Oct 2020 13:37:40 -0000 From: "Laurent Bercot" To: musl@lists.openwall.com, "Rich Felker" , "Arjun Shankar" Cc: "Florian Weimer" Date: Fri, 23 Oct 2020 13:37:29 +0000 Message-Id: In-Reply-To: References: <1924902939.18027073.1603105167534.JavaMail.zimbra@redhat.com> <805098991.18032044.1603106011330.JavaMail.zimbra@redhat.com> <20201020010855.GE17637@brightrain.aerifal.cx> User-Agent: eM_Client/8.0.3385.0 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedujedrkedtgdeigecutefuodetggdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdguihgvthhlihgstgesshhkrghrnhgvthdrohhrgheqnecuggftrfgrthhtvghrnheplefgjedtteeutddvuddvheejgfdvgfeftdejieegfeevfffhueekfeeuueduteejnecuffhomhgrihhnpehskhgrrhhnvghtrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpohhuth Subject: Re: [musl] Plans to remove nscd in Fedora >My opinion is that we want something much thinner than nscd to provide >NSS for statically linked applications, and that such an interface >should not provide caching. If we really wanted we could keep the nscd >socket interface but implement an NSS daemon for this e.g. nssd that would >just run all the time and could be depended upon by static applications. >It would have to be well audited and very simple. > >The caching that nscd does has many legacy problems that are better solved >and maintained by other daemons that implement a split NSS module approach >(as Florian notes). There is such an approach already: https://skarnet.org/software/nsss/ It works, it just has not been integrated into distributions yet because musl distributions, at the moment, are not much interested in NSS functionality, and glibc distributions simply use nsswitch. If there is interest, I'll be happy to cooperate with any relevant project to make sure it's suited to its needs. -- Laurent