From owner-freebsd-current  Mon Jun 19 13:29:04 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA09225
          for current-outgoing; Mon, 19 Jun 1995 13:29:04 -0700
Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA09218
          for <current@FreeBSD.org>; Mon, 19 Jun 1995 13:28:57 -0700
Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA09361; Mon, 19 Jun 1995 16:28:30 -0400
Date: Mon, 19 Jun 1995 16:28:30 -0400
From: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu>
Message-Id: <9506192028.AA09361@halloran-eldar.lcs.mit.edu>
To: Mark Murray <mark@grondar.za>
Cc: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu>,
        "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, current@FreeBSD.org
Subject: Re: Crypto code - an architectural proposal. 
In-Reply-To: <199506192012.WAA00163@grumble.grondar.za>
References: <199506192012.WAA00163@grumble.grondar.za>
Sender: current-owner@FreeBSD.org
Precedence: bulk

<<On Mon, 19 Jun 1995 22:12:26 +0200, Mark Murray <mark@grondar.za> said:

> If the state department has a problem (or potential problem) with the
> crypt(3) in libdescrypt, why is there _no_ problem with the MD5 crypt(3)?
> They are functionally equivalent. Was the MD5 version even vetted?

Because the libdescrypt version is implemented by calling a whacked-up
version of DES, whereas MD5 was designed from the start to be
exportable.

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@lcs.mit.edu  | Shashish is the bonding of hearts in spite of distance.
Opinions not those of| It is a bond more powerful than absence.  We like people
MIT, LCS, ANA, or NSA| who like Shashish.  - Claude McKenzie + Florent Vollant