Date: Wed, 3 Mar 1999 18:51:48 -0600 (CST) From: Jonathan Fosburgh <wotan@dorm-36314.rh.uh.edu> To: GVB <gvb@tns.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: compat_2_2 Message-ID: <Pine.BSF.4.05.9903031847250.16269-100000@dorm-36314.rh.uh.edu> In-Reply-To: <4.1.19990303164129.00bd48e0@abused.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Mar 1999, GVB wrote:
> At 06:29 PM 3/3/99 -0600, you wrote:
> >On Wed, 3 Mar 1999, GVB wrote:
> >
> >> At 06:17 PM 3/3/99 -0600, you wrote:
> >> >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.
> >>
> >> Ok, but how come when I boot single user, run the passwd command, it
> >> recompiles the pw database and I can login fine after that?
> >>
> >> GVB
> >>
> >>
> >Compare a working password entry and a nonworking one in
> >/etc/master.passwd. They should both be the same format. If one of them
> >is a different format then there is some kind of problem. If you have
> >always used the standard MD5 then the old passwords should be $1$. If the
> >working password does not have this then my guess is that login and passwd
> >are not working properly. My suggestion would be to make world and see if
> >things come out right afterward. Of course, you can always seek a second
> >opinion. :)
>
> Ok, I just took a look and the passwords that work are the $1$ ones... the
> only user with that style passwd in master.passwd is root because I booted
> into single user and changed the password with the passwd command and now I
> can login.. all the old passwords from the 2.2.8 machine dont work. All I
> did was a standard upgrade from 2.2.8 to 3.1. My machines that were 3.0
> that went to 3.1 all had the passwords WITHOUT the $1$ and they all
> upgraded fine. Any ideas?
>
How did you do the upgrade? Binary? make upgrade? make
aout-to-elf{build,install}? ? My make aout-to-elf{build,install}worked.
However, I do now remember that some accounts that had not been accessed
in a very long time were the format without $1$. These accounts probably
have not been used since 2.2.5 or maybe even 2.2.2, and I generally remain
fairly current on releases, so we are talking over a year. Unfortunately
I do not know how to fix this problem, but I hope that maybe someone more
knowledgable on the subject will explain what's going on, all I know I had
to pick up on the fly, and fortunately my problems were solved by some
very simple hacking of one program and recompiling another.
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9903031847250.16269-100000>