From owner-freebsd-questions Fri Aug 9 22:12:16 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA04479 for questions-outgoing; Fri, 9 Aug 1996 22:12:16 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts7-line12.uoregon.edu [128.223.150.59]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA04474 for ; Fri, 9 Aug 1996 22:12:13 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id WAA00347; Fri, 9 Aug 1996 22:12:13 -0700 (PDT) Date: Fri, 9 Aug 1996 22:12:13 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Ian Kallen cc: questions@freebsd.org Subject: Re: poppassd In-Reply-To: <199608081213.MAA03840@gamespot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 8 Aug 1996, Ian Kallen wrote: > I compiled poppassd to permit users who are accessing the pop server > via Eudora to change their passwords but I think the program is > choking on the fact that freebsd has the password file in a dbm > database. Anybody successfully modified it to read and write to the > dbm file instead of a plain text /etc/passwd? If ya can save us the > coding, that'd be great! Thanks! I *highly* recommend people do __NOT__ use Eudora to change passwords. It even ruins pop on the University's Suns. They should telnet & login and use passwd to change their password instead. This allows you to enforce minumum password standards too, which the U of O does. We had a situation where popd picked up the change but login didn't, and it made a *huge* mess. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major