From owner-freebsd-isp  Mon Mar  5  9:43:42 2001
Delivered-To: freebsd-isp@freebsd.org
Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194])
	by hub.freebsd.org (Postfix) with ESMTP id 3E8CB37B71A
	for <freebsd-isp@FreeBSD.ORG>; Mon,  5 Mar 2001 09:43:38 -0800 (PST)
	(envelope-from so@server.i-clue.de)
Received: from i-clue.de (automatix.i-clue.de [192.168.0.112])
	by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id TAA03796;
	Mon, 5 Mar 2001 19:49:37 +0100
Message-ID: <3AA3D07E.E0487684@i-clue.de>
Date: Mon, 05 Mar 2001 18:44:30 +0100
From: Christoph Sold <so@server.i-clue.de>
Reply-To: so@server.i-clue.de
X-Mailer: Mozilla 4.75 [de] (WinNT; U)
X-Accept-Language: de
MIME-Version: 1.0
To: Bob Martin <bob@buckhorn.net>
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Bad password file after upgrade crash
References: <3AA18E5C.797E4CA3@buckhorn.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



Bob Martin schrieb:
> 
> While doing a binary upgrade from 3.3-Stable to 4.2-Release, we crashed
> (broken pipe)
> We restored the system from tape, but now it doesn't recognize any
> passwords.
> 
> We've tried blowing away the db files and running pwd_mkdb, to no avail.
> Any suggestions would be more than welcome.

Check your master.passwd encryption scheme matches the libraries. If the
password field reads starts with $1$, it is MD5 encrypted, otherwise,
it's DES encrypted. Makle sure your new system has the appropriate
libraries.

HTH
-Christoph Sold

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message