From owner-freebsd-questions Tue Jan 6 05:43:11 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11557 for questions-outgoing; Tue, 6 Jan 1998 05:43:11 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from acaxp (acaxp.physik.rwth-aachen.de [137.226.33.200]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA11530 for ; Tue, 6 Jan 1998 05:42:50 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto by acaxp; (5.65v3.2/1.1.8.2/17Mar96-1112AM) id AA07976; Tue, 6 Jan 1998 14:42:40 +0100 Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.8/8.6.9) id OAA01901 for freebsd-questions@freefall.cdrom.com; Tue, 6 Jan 1998 14:42:42 +0100 (MET) Date: Tue, 6 Jan 1998 14:42:42 +0100 (MET) From: Christoph Kukulies Message-Id: <199801061342.OAA01901@gil.physik.rwth-aachen.de> To: freebsd-questions@freefall.FreeBSD.org Subject: des and md5 passwd encryption - problem Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I upgraded a machine from 2.0.5 to 2.2.5 yesterday and preserved my old master.passwd. Then I installed libdescrypt.so.2.0 from a machine in our network since the binary dist doesn't have the libdes stuff (I took a version from internat.freebsd.org). Since users with MD5 passwords seem to be unable to login. I also noted that when a user had a md5 passwd string in the old master.passwd ($1$...) and you give him a new one he gets a des password starting with $1. Formerly libdes (crypt.c) took care for this and gave him a MD5 password again although des was enabled (via the libcrypt link). How can I get out of this mess? I don't want to tell all my users to change their passwords. Can someone shed some light on what's changed? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de