From owner-freebsd-current Mon Dec 16 08:40:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA16301 for current-outgoing; Mon, 16 Dec 1996 08:40:42 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA16296 for ; Mon, 16 Dec 1996 08:40:39 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vZg52-0003w4C; Mon, 16 Dec 96 08:39 PST Received: from critter.tfs.com (localhost [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id RAA12327; Mon, 16 Dec 1996 17:40:03 +0100 (MET) To: peter@spinner.DIALix.COM (Peter Wemm) cc: freebsd-current@freebsd.org Subject: Re: Plan for integrating Secure RPC -- comments wanted In-reply-to: Your message of "16 Dec 1996 15:20:33 GMT." <593pc1$k40$1@haywire.DIALix.COM> Date: Mon, 16 Dec 1996 17:40:02 +0100 Message-ID: <12325.850754402@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Why don't we just give in and make a dual-mode libcrypt with the >exportable des one-way hash code like all the other vendors are doing? >(and of course, the MD5 hash code) I'm game. Although this doesn't solve the problem with /bin/ed and other legitimate users of DES, secure RPC for instance. >Anyway, the problem then becomes.. How do you choose the default encryption >type for the new merged crypt() when it doesn't have a precedent to go on? You check which one root used and use the same ? >I know this doesn't have much to do with Secure RPC, but it would get rid of >the dual versions of /sbin/init, /bin/ed, libcrypt etc. I would like libcrypt >to go away and become a stub library just like libresolv/libgnumalloc. I agree. But is the source for the DES-hash exportable ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.