From owner-freebsd-questions Thu Mar 4 10:23:54 1999 Delivered-To: freebsd-questions@freebsd.org Received: from abused.com (abused.com [204.216.142.63]) by hub.freebsd.org (Postfix) with ESMTP id 55ED815077 for ; Thu, 4 Mar 1999 10:23:52 -0800 (PST) (envelope-from gvbmail@tns.net) Received: from gvb (gvb.tns.net [204.216.245.137]) by abused.com (8.9.3/I feel abused.) with SMTP id KAA26437; Thu, 4 Mar 1999 10:26:20 -0800 (PST) Message-Id: <4.1.19990304102515.00a69290@abused.com> X-Sender: gvbmail@mail.tns.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 04 Mar 1999 10:26:19 -0800 To: Patrick Seal From: GVB Subject: Re: clarity on password crypt Cc: Nathan Ahlstrom , freebsd-questions@FreeBSD.ORG In-Reply-To: References: <4.1.19990304094438.00bcfa80@abused.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh, you are correct! I could not ssh into the machine, but I figured out I just needed to recompiled ssh, I do not know enough about how ssh compiles crypt into the binary, but a simple recompile fixed all problems. Thanks for the help! GVB At 01:15 PM 3/4/99 -0500, Patrick Seal wrote: > >> 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! > >On Thu, 4 Mar 1999, GVB wrote: > >> At 11:00 AM 3/4/99 -0600, Nathan Ahlstrom wrote: >> > >> >GVB 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