Date: Thu, 4 Mar 1999 13:15:24 -0500 (EST) From: Patrick Seal <patseal@hyperhost.net> To: GVB <gvbmail@tns.net> Cc: Nathan Ahlstrom <nrahlstr@winternet.com>, freebsd-questions@FreeBSD.ORG Subject: Re: clarity on password crypt Message-ID: <Pine.BSF.4.05.9903041313590.1622-100000@foobar.hyperhost.net> In-Reply-To: <4.1.19990304094438.00bcfa80@abused.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Isnt there some easier way to make sure everything gets fixed? What could be easier? 1) Single-user mode 2) change symlink 3) done I believe that's it! ------------------------------------ _____________________________________ Patrick Seal |"Microsoft isn't evil, they just make <patseal@hyperhost.net> | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds hosting and Design http://www.freebsd.org - http://www.linux.org On Thu, 4 Mar 1999, GVB wrote: > At 11:00 AM 3/4/99 -0600, Nathan Ahlstrom wrote: > > > >GVB <gvbmail@tns.net> wrote: > >> Since I have been having problems with my passwd files on upgrades from > >> 2.2.8 to 3.1 but not on upgrades from 3.0 to 3.1 I wanted to clear a few > >> things up. What style of crypt is listed here; > >> > >> root:6rKXEwLNbIiSw:0:0::0:0:root?:/root:/usr/local/bin/bash > >> > >> And what style of crypt has the $1$ in the password field and is about > >> twice as long? > > > >The one with the $1$ is the md5 crypt, it is the default. > > > >> Which one of these is default? Because all my old machines 2.2.7, 2.2.8 > >> etc have the style that I listed above, including my 3.0 machines. When I > >> went from 3.0 -> 3.1 nothing changed. When I went from 2.2.8 -> 3.1 it > >> changed and my passwords like the one listed above dont work now. > > > >You might should adjust the symlink for the /usr/lib/*crypt* libraries. (I > >think ;) > > > >portage% ls -al *crypt* > >lrwxrwxrwx 1 root wheel 11 Feb 24 15:10 libcrypt.a -> libscrypt.a > >lrwxrwxrwx 1 root wheel 12 Feb 24 15:10 libcrypt.so -> libscrypt.so > >lrwxrwxrwx 1 root wheel 14 Feb 24 15:10 libcrypt.so.2 -> libscrypt.so.2 > >lrwxr-xr-x 1 root bin 16 Jan 18 19:02 libcrypt.so.2.0 -> > >libscrypt.so.2.0 > >lrwxr-xr-x 1 root bin 13 Jan 18 19:02 libcrypt_p.a -> libscrypt_p.a > >-r--r--r-- 1 root wheel 13018 Feb 28 17:05 libdescrypt.a > >lrwxr-xr-x 1 root wheel 16 Feb 28 17:05 libdescrypt.so -> > >libdescrypt.so.2 > >-r--r--r-- 1 root wheel 12989 Feb 28 17:05 libdescrypt.so.2 > >-r--r--r-- 1 bin bin 16698 Jan 16 23:22 libdescrypt.so.2.0 > >-r--r--r-- 1 root wheel 14750 Feb 28 17:05 libdescrypt_p.a > >-r--r--r-- 1 root wheel 6198 Feb 28 17:05 libscrypt.a > >lrwxr-xr-x 1 root wheel 14 Feb 28 17:05 libscrypt.so -> libscrypt.so.2 > >-r--r--r-- 1 root wheel 7607 Feb 28 17:05 libscrypt.so.2 > >-r--r--r-- 1 bin bin 12579 Sep 4 11:03 libscrypt.so.2.0 > >-r--r--r-- 1 root wheel 6688 Feb 28 17:05 libscrypt_p.a > > > > > >The libcrypt* symlink points to libscrypt* by default. You need to adjust > >these symlinks in your /usr/lib to point to the respective libdescrypt* > >instead of libscrypt*. The upgrade may have restored your symlinks to the > >default? > > > >Good Luck, > > > >Nathan > > Ok, I reset the symlinks to reflect the des crypts.. now when I run the > passwd command and pwd_mkdb it encyrpts it into my original DES format. > BUT, when I try to login it doesnt accept the password now.. the same > condition I had before, I have to boot into single user mode and switch the > crypt symlinks back to change the password back to MD5 then I can login. > Do I need to recompile login and anything else than uses the crpyt libs?? > Isnt there some easier way to make sure everything gets fixed? > > Thanks again, > > GVB > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > 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.9903041313590.1622-100000>