From owner-freebsd-current Sun Nov 12 18:42:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA00179 for current-outgoing; Sun, 12 Nov 1995 18:42:26 -0800 Received: from gaia.coppe.ufrj.br (root@gaia.coppe.ufrj.br [146.164.63.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA00141 for ; Sun, 12 Nov 1995 18:42:21 -0800 Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.6.11/8.6.9) id AAA07777; Mon, 13 Nov 1995 00:42:00 -0200 From: Joao Carlos Mendes Luis Message-Id: <199511130242.AAA07777@gaia.coppe.ufrj.br> Subject: Re: Dual personality crypt. To: current@freefall.freebsd.org Date: Mon, 13 Nov 1995 00:41:59 -0200 (EDT) In-Reply-To: <199511122033.WAA10257@zibbi.mikom.csir.co.za> from "John Hay" at Nov 12, 95 10:33:20 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1081 Sender: owner-current@FreeBSD.org Precedence: bulk > > Mark, Great idea. > > > > I think you should offer an option to make new encryptions > > a) DES > > b) MD5 > > c) "the same as before" > > > > to make it general. I don't know if you can do this without changing > > the passwd program btw. > > > Yes, I like this. I would not like to be forced to have ALL new passwords > using des. Hey everybody... I hope you remember that password entries could be used by other programs rather than login, su and passwd. If we change the crypt(3) function drastically we may have to do lot's of new ports to deal with these new incompatibilities. I think it's better to have the problems we have now rather than making a new incompatibilty when comparing to other systems. Think of this before new "great" ideas. If this change is REALLY transparent, do it. If not, let it be an option, p'p'p'p'pleaaaase. Jonny PS: No, I'm not Roger Rabbit... :) -- Joao Carlos Mendes Luis jonny@coe.ufrj.br +55 21 290-4698 ( Job ) jonny@adc.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro