Date: Mon, 16 Dec 1996 17:40:02 +0100 From: Poul-Henning Kamp <phk@critter.tfs.com> To: peter@spinner.DIALix.COM (Peter Wemm) Cc: freebsd-current@freebsd.org Subject: Re: Plan for integrating Secure RPC -- comments wanted Message-ID: <12325.850754402@critter.tfs.com> In-Reply-To: Your message of "16 Dec 1996 15:20:33 GMT." <593pc1$k40$1@haywire.DIALix.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
>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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12325.850754402>