From owner-freebsd-current Thu Feb 29 08:55:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA22290 for current-outgoing; Thu, 29 Feb 1996 08:55:25 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA22281 for ; Thu, 29 Feb 1996 08:55:11 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.3/8.7.3) with ESMTP id SAA05200; Thu, 29 Feb 1996 18:52:57 +0200 (SAT) Message-Id: <199602291652.SAA05200@grumble.grondar.za> To: invalid opcode cc: Paul Traina , Adam David , Mark Murray , freebsd-current@FreeBSD.org Subject: Re: New Dual-personality crypt Date: Thu, 29 Feb 1996 18:52:56 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org Precedence: bulk invalid opcode wrote: > 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. This is what I would like, too. I do not beleive that it is at all valid for a sysadmin to allow users to choose their encryption type - this is quite frankly none of the users' business. I'll get to it. (Read: I'll add it to my list) M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key