From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1548 Path: news.gmane.org!not-for-mail From: "Arvid E. Picciani" Newsgroups: gmane.linux.lib.musl.general Subject: Re: Design for extensible =?UTF-8?Q?passwd=5B/shadow=3F=5D?= =?UTF-8?Q?=20db=20support?= Date: Sun, 12 Aug 2012 21:10:16 +0200 Message-ID: References: <20120812053802.GA10971@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1344798638 15364 80.91.229.3 (12 Aug 2012 19:10:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 12 Aug 2012 19:10:38 +0000 (UTC) To: Original-X-From: musl-return-1549-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 12 21:10:37 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1T0dYY-0000gh-9l for gllmg-musl@plane.gmane.org; Sun, 12 Aug 2012 21:10:34 +0200 Original-Received: (qmail 3631 invoked by uid 550); 12 Aug 2012 19:10:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 3623 invoked from network); 12 Aug 2012 19:10:33 -0000 In-Reply-To: <20120812053802.GA10971@brightrain.aerifal.cx> X-Sender: aep@exys.org User-Agent: Roundcube Webmail/0.5.4 Xref: news.gmane.org gmane.linux.lib.musl.general:1548 Archived-At: On Sun, 12 Aug 2012 01:38:02 -0400, Rich Felker wrote: > What I'm looking for is a way to allow musl to access user data > that's > not provided with flat files in /etc, I'm not sure why user auth is in libc in the first place. These things change, and a libc is not something i would see as a layer where system design should happen. > [..] abominations like RPC. [..] This assumes RPC is the way it is out of bad intent, while it really grew out of exactly the same requirements. Things don't get better by rewriting them without changing the design. > [..] can query a local daemon [..] > The first main question is what protocol to use. well, so use the existing rpc. it fullfills the given requirements, and is compatible with the stuff out there. > Alternatively, we could make musl speak an existing query language > (e.g. LDAP) directly And pull even more policy into libc? Then everyone has to patch libc to adapt to the local ldap layout? or another config? There is a need for the things you want to do here, but i think this is the line where it's time to go into higher layers. -- Arvid E. Picciani