From owner-cvs-all Mon Mar 18 5:11:34 2002 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6122337B41A; Mon, 18 Mar 2002 05:11:28 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2IDBKk24996; Mon, 18 Mar 2002 08:11:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 18 Mar 2002 08:11:20 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mark Murray Cc: cjclark@alum.mit.edu, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/chpass chpass.c pw_copy.c pw_copy.h In-Reply-To: <200203181302.g2ID28H5020685@grimreaper.grondar.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 18 Mar 2002, Mark Murray wrote: > > This is all quite a mess. We have chpass(8) using __pw_scan from libc > > and source in vipw(8), and PAM modules sharing all of this code > > too. Wouldn't the Right Thing be to put these functions in a library > > somewhere? I think NetBSD has a lot of this stuffed in libutil. > > There is a lot of password-related stuff spread about the tree in this > messy way (chpass, vipw, chsh(and friends), passwd and so on). I would > vote very strongly for such a change. > > I started doing it some time ago, and lost track in the tangled thread. A remarkably number of userland tools assume that access to passwd information is in libc. Would such a change move this completely out of libc and require modifying the linkages involved for all of these, or is this a lower-level kind of thing? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message