From owner-freebsd-current Tue Jun 20 11:20:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01855 for current-outgoing; Tue, 20 Jun 1995 11:20:25 -0700 Received: (from phk@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA01845 ; Tue, 20 Jun 1995 11:20:23 -0700 From: Poul-Henning Kamp Message-Id: <199506201820.LAA01845@freefall.cdrom.com> Subject: Re: The great crypt reshuffle To: mark@grondar.za (Mark Murray) Date: Tue, 20 Jun 1995 11:20:22 -0700 (PDT) Cc: rgrimes@gndrsh.aac.dev.com, Wollman@halloran-eldar.lcs.mit.edu, gibbs@freefall.cdrom.com, current@freebsd.org In-Reply-To: <199506201457.QAA02441@grumble.grondar.za> from "Mark Murray" at Jun 20, 95 04:57:22 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1147 Sender: current-owner@freebsd.org Precedence: bulk > 2) crypt(3) and friends in libcipher to be replaced with faster code > from same author as libdes, and to merge with libdes. (I know, not > much concensus here - I'm just pushing my luck) > 3) libcrypts containing _only_ des crypt(3) and md5 crypt(3) to remain > unchanged (Except perhaps for newer code in des crypt(3)) to maintain > possible foreign licensing. One selected as the _real_ libcrypt by > symlink. You can even consider making the DES crypt(3) take MD5 crypt(3) strings too. You can recognize them on the $1$ at the start. That would allow a system to use either type and this the good ol' trick of sending a encrypted password in an email would still be good. > 4) (Very little discussion here) Other libraries containing crypto > code (ssl, rsa, md4, idea (where legal/appropriate)) be placed in md2, md4 and md5 isn't export-restricted. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ?