From owner-freebsd-questions Thu Mar 4 9: 1:49 1999 Delivered-To: freebsd-questions@freebsd.org Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (Postfix) with ESMTP id 81ACD15076 for ; Thu, 4 Mar 1999 09:01:46 -0800 (PST) (envelope-from nrahlstr@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id LAA29676; Thu, 4 Mar 1999 11:01:13 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma029623; Thu, 4 Mar 99 11:00:52 -0600 Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id LAA16315; Thu, 4 Mar 1999 11:00:53 -0600 (CST) Message-ID: <19990304110053.D15184@winternet.com> Date: Thu, 4 Mar 1999 11:00:53 -0600 From: Nathan Ahlstrom To: GVB , freebsd-questions@FreeBSD.ORG Subject: Re: clarity on password crypt References: <4.1.19990304081727.00bb39f0@abused.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19990304081727.00bb39f0@abused.com>; from GVB on Thu, Mar 04, 1999 at 08:19:54AM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- Nathan Ahlstrom nrahlstr@winternet.com http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message