From owner-freebsd-questions Wed Mar 3 16:18:30 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dorm-36314.rh.uh.edu (Dorm-36314.RH.UH.EDU [129.7.141.218]) by hub.freebsd.org (Postfix) with ESMTP id 9379C15660 for ; Wed, 3 Mar 1999 16:18:28 -0800 (PST) (envelope-from wotan@dorm-36314.rh.uh.edu) Received: from localhost (wotan@localhost) by dorm-36314.rh.uh.edu (8.9.2/8.9.2) with ESMTP id SAA16290; Wed, 3 Mar 1999 18:17:54 -0600 (CST) (envelope-from wotan@dorm-36314.rh.uh.edu) Date: Wed, 3 Mar 1999 18:17:54 -0600 (CST) From: Jonathan Fosburgh Reply-To: jef53313@bayou.uh.edu To: Thomas David Rivers Cc: gvb@tns.net, freebsd-questions@FreeBSD.ORG Subject: Re: compat_2_2 In-Reply-To: <199903032300.SAA00620@lakes.dignus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, Thomas David Rivers wrote: > > > > Ok, so my upgrade from 2.2.8 to 3.1 upgraded the crypt() stuff, but now, > > because of this upgrade, none of my old master.passwd files work.. and on > > systems with thousands of users I cant sit here and change every users > > password.. there has got to be a way to make it backwards compatible, or > > convert old to new.. any ideas? > > > > GVB > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > You shouldn't be having these problems... I've used the same password > file basically since 386BSD. > > If you have password entries that look like $1$xxxx - then you were using > MD5 crypt and not DES script. > > I'm guessing you were using one or the other before and have now > (accidently) changed. > > You should have no problems using the previous entries. > > The DES stuff even works across other systems; I used to cut-and-paste > passwords from HP and Sun boxes into /etc/master.passwd with no problem. > > Anyway, although there isn't much specific help in this note - I hope > it is encouraging... I'm confident that you won't have to change all of > your entries. According to some literature I have read, the FreeBSD crypt is a different format (perhaps this is just from Linux) with the seed in positions four and five. The old passwords from the application to which I have been referring were in the correct form ($1$) but the old a.out executable began reading passwords expecting the seed in positions 1 and 2. Recompiling that app to elf solved that problem, and the old passwords started working again. What I am trying to say from all this is that perhaps, if the upgrade was not performed correctly, something could be causing login to look for the seed in positions 1 and 2 as opposed to 4 and 5. Jonathan Fosburgh Geotechnician Snyder Oil Corporation Houston, TX Home Page: http://www.geocities.com/vienna/1498 Manager, FreeBSD Webring: http://www.geocities.com/vienna/1498/computer/freebsdring.html ICQ: 32742908 AIM: Namthorien To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message