From owner-freebsd-current  Mon Dec 16 14:54:55 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA11212
          for current-outgoing; Mon, 16 Dec 1996 14:54:55 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA11200
          for <freebsd-current@freebsd.org>; Mon, 16 Dec 1996 14:54:52 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA02252; Mon, 16 Dec 1996 15:53:12 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199612162253.PAA02252@phaeton.artisoft.com>
Subject: Re: Plan for integrating Secure RPC -- comments wanted
To: phk@critter.tfs.com (Poul-Henning Kamp)
Date: Mon, 16 Dec 1996 15:53:12 -0700 (MST)
Cc: peter@spinner.DIALix.COM, freebsd-current@freebsd.org
In-Reply-To: <12325.850754402@critter.tfs.com> from "Poul-Henning Kamp" at Dec 16, 96 05:40:02 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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.

Heh.  "Making RPC calls the government can't read is not legitimate use".


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.