From: Mike Gurski <mgursk1@gl.umbc.edu>
To: cypherpunks@toad.com
Message Hash: 93d9b20a3177902d3d52983e092ec4e3e1700e9691d8f4a46828b03f431b7ba8
Message ID: <Pine.SGI.3.91.960125105552.5489A-100000@umbc10.umbc.edu>
Reply To: <199601250034.TAA09745@toxicwaste.media.mit.edu>
UTC Datetime: 1996-01-25 18:11:03 UTC
Raw Date: Fri, 26 Jan 1996 02:11:03 +0800
From: Mike Gurski <mgursk1@gl.umbc.edu>
Date: Fri, 26 Jan 1996 02:11:03 +0800
To: cypherpunks@toad.com
Subject: Re: Crippled Notes export encryption
In-Reply-To: <199601250034.TAA09745@toxicwaste.media.mit.edu>
Message-ID: <Pine.SGI.3.91.960125105552.5489A-100000@umbc10.umbc.edu>
MIME-Version: 1.0
Content-Type: text/plain
On Wed, 24 Jan 1996, Derek Atkins wrote:
> > How exactly are crypto-hooks defined? This restriction seems orders
> > of magnitude more bogus than even the ban on exporting actual
> > encryption.
>
> Very vaguely. If I have a function that does something like this:
>
> authenticate (args)
> {
> ...
>
> des_encrypt ();
> ...
> }
>
> I would have to remove the des_encrypt() call from the authenticate()
> routine before it can be exported...
Would removing the call to des_encrypt() and replacing it with a
comment violate the restriction? something like:
authenticate (args)
{
...
/* squeamish ossifrage */
...
}
--
|\/|ike Gurski mgursk1@gl.umbc.edu FidoNet: 1:261/1062
http://www.gl.umbc.edu/~mgursk1/ finger -l for PGP public key |Member,
1024/39B5BADD PGP Keyprint=3493 A994 B159 48B7 1757 1E4E 6256 4570| Team
My opinions are mine alone, even if you should be sharing them. | OS/2
Return to January 1996
Return to “Ulf_Moeller@public.uni-hamburg.de (Ulf Moeller)”