From owner-freebsd-current  Wed Feb 28 23:25:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA11492
          for current-outgoing; Wed, 28 Feb 1996 23:25:34 -0800 (PST)
Received: from nervosa.com (root@nervosa.com [192.187.228.86])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA11477
          for <freebsd-current@freebsd.org>; Wed, 28 Feb 1996 23:25:31 -0800 (PST)
Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.4/nervosa.com.2) with SMTP id XAA23182; Wed, 28 Feb 1996 23:24:37 -0800 (PST)
Date: Wed, 28 Feb 1996 23:24:37 -0800 (PST)
From: invalid opcode <coredump@nervosa.com>
To: Paul Traina <pst@shockwave.com>
cc: Adam David <adam@veda.is>, Mark Murray <mark@grondar.ZA>,
        freebsd-current@freebsd.org
Subject: Re: New Dual-personality crypt 
In-Reply-To: <199602290531.VAA01367@precipice.shockwave.com>
Message-ID: <Pine.BSF.3.91.960228231554.23102A-100000@nervosa.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
Precedence: bulk

On Wed, 28 Feb 1996, Paul Traina wrote:

> I would strongly suggest that users NOT be allowed to select their method
> unless the sysadmin explicitly enables it... and I think a sysadmin would

I strongly agree with this also. a: what do users' care what encryption 
algorithim is used, it's not something that will make any kind of 
difference for them. b: We could make passwd(8) generate md5 passwords by 
default, and have, for instance, a "-e" flag to change the encryption 
method; or we could add another file to /etc for instance "passwd.conf" 
that has the configuration information stored there. I would opt for 
passwd.conf.

== Chris Layne ==============================================================
== coredump@nervosa.com ================= http://www.nervosa.com/~coredump ==