From owner-freebsd-hackers Wed Jan 17 07:00:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA14743 for hackers-outgoing; Wed, 17 Jan 1996 07:00:16 -0800 (PST) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA14730 for ; Wed, 17 Jan 1996 07:00:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by spooky.rwwa.com (8.6.11/8.6.9) with SMTP id KAA07526 for ; Wed, 17 Jan 1996 10:00:01 -0500 Message-Id: <199601171500.KAA07526@spooky.rwwa.com> X-Authentication-Warning: spooky.rwwa.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.5.3 12/28/94 To: freebsd-hackers@freebsd.org Subject: Bugs in passwd mgmt stuff Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 17 Jan 1996 10:00:01 -0500 From: Robert Withrow Sender: owner-hackers@freebsd.org Precedence: bulk > I don't like the idea of a delete user script. There should be, at least, programmatic support for deleting passwd and group entries. There is nothing for that now. Also, there should be programmatic ways of changing the passwd (other than being forced to use expect/passwd or something.) [In my case I have a system a system where the passwd database and another database need to be kept in sync. While we are at it, I have noticed the following errors in 2.1 WRT this: 1) There is no way to delete entries from passwd or group without just manually doing it. 2) crypt(3) says that the ``setting'' string is 9 characters beginning with ''_'', but by trial and error, it seems that the passwords in the master.passwd file are *not* generated this way. 3) chpass -p doesn't seem to work at all. 4) Adduser fails to correctly set the ownership of the home directory. (In fact, adduser often seems to have ``strange'' behavior. ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM