From owner-freebsd-security Wed Jun 6 9:20:28 2001 Delivered-To: freebsd-security@freebsd.org Received: from slis-two.lis.fsu.edu (slis-two.lis.fsu.edu [128.186.72.102]) by hub.freebsd.org (Postfix) with ESMTP id B7B5437B401 for ; Wed, 6 Jun 2001 09:20:23 -0700 (PDT) (envelope-from david@slis-two.lis.fsu.edu) Received: from localhost (david@localhost) by slis-two.lis.fsu.edu (8.11.1/8.11.1) with ESMTP id f56GM6S50951; Wed, 6 Jun 2001 12:22:06 -0400 (EDT) (envelope-from david@slis-two.lis.fsu.edu) Date: Wed, 6 Jun 2001 12:22:06 -0400 (EDT) From: David Miner To: Olivier Nicole Cc: Subject: Re: Encrypted passwords In-Reply-To: <200106061609.XAA02163@bazooka.cs.ait.ac.th> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 6 Jun 2001, Olivier Nicole wrote: > >But when I encrypt them and put them in the passwd file, they do not allow > >the user to log in.I have to use the passwd program to manually change > >them to the same password that I wanted originally.Thus I believe the > >problem lies in the encryption method or how it is being passwd to the > >chpass program. > > Hummm, I think nowdays passwords are not kept in a plain file but in a > .db file. Can't it be the problem? > > Olivier > No, the chpass function takes care calling mk-pwd and putting them in the .db file. Otherwise nothing would be there when I look at it with vipw. It appears that what is being passed by the crypt function is not what is making it into the passwd file. At a SWAG. David --------------------------------------------------------------------- David R. Miner miner@lis.fsu.edu Systems Integrator voice: 850-644-8107 School of Information Studies fax: 850-644-6253 Florida State University Tallahassee, FL 32306-2100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message