From owner-freebsd-isp Tue Feb 10 13:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20050 for freebsd-isp-outgoing; Tue, 10 Feb 1998 13:39:57 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20042 for ; Tue, 10 Feb 1998 13:39:52 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA29729; Wed, 11 Feb 1998 08:39:36 +1100 (EST) Date: Wed, 11 Feb 1998 08:39:34 +1100 (EST) From: "Daniel O'Callaghan" To: Benjamin Gras cc: isp@FreeBSD.ORG Subject: Re: Passwords.. In-Reply-To: <199802101644.RAA04045@support.euronet.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 10 Feb 1998, Benjamin Gras wrote: > As for a practical solution (I'd say): > Why not make FreeBSD use the DES-based passwords, and patch login(1) to > hash (using MD5-style) the password when you've verified the plaintext > entered password is correct (by hashing it DES-style as login(1) will do), > writing it back into the (master.) passwd file? This way you can do the > conversion, in a way.. Why bother? If you just want Linux passwords readable by FreeBSD, install the DES kit from ftp.internat.freebsd.org and use both DES and MD5 on FreeBSD. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message