From owner-freebsd-questions Tue Apr 1 22:51:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA10644 for questions-outgoing; Tue, 1 Apr 1997 22:51:00 -0800 (PST) Received: from starfire.mn.org (root@starfire.skypoint.net [199.86.32.187]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA10639 for ; Tue, 1 Apr 1997 22:50:55 -0800 (PST) Received: (from john@localhost) by starfire.mn.org (8.8.5/1.1) id AAA02841 for questions@FreeBSD.org; Wed, 2 Apr 1997 00:50:51 -0600 (CST) From: John Lind Message-Id: <199704020650.AAA02841@starfire.mn.org> Subject: DES and MD5 To: questions@FreeBSD.org (FreeBSD questions) Date: Wed, 2 Apr 1997 00:50:51 -0600 (CST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Is there a configuration such that we can import all of our existing DES-based passwords, but as people update them, to create MD5 passwords in their place? It appears that MD5 passwords are understood in the lastest releases of FreeBSD even if I load up DES (which was handy), but new passwords are then created via DES. Or am I confused? John Lind, Starfire Consulting Services E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417