1996-12-23 - Re: [NOT NOISE] Microsoft Crypto Service Provider API

Header Data

From: jim bell <jimbell@pacifier.com>
To: marc@cygnus.com>
Message Hash: 0a0b3eeaa88d40e8721dbeb2d98150cce3c5f4836711506f6194b91ffcefd512
Message ID: <199612230332.TAA29587@mail.pacifier.com>
Reply To: N/A
UTC Datetime: 1996-12-23 03:32:53 UTC
Raw Date: Sun, 22 Dec 1996 19:32:53 -0800 (PST)

Raw message

From: jim bell <jimbell@pacifier.com>
Date: Sun, 22 Dec 1996 19:32:53 -0800 (PST)
To: marc@cygnus.com>
Subject: Re: [NOT NOISE] Microsoft Crypto Service Provider API
Message-ID: <199612230332.TAA29587@mail.pacifier.com>
MIME-Version: 1.0
Content-Type: text/plain


At 07:36 AM 12/18/96 -0800, geeman@best.com wrote:
>
>Microsoft had to agree to validate crypto binaries against
>a signature to make sure they weren't tampered with, in 
>exchange for shipping crypto-with-a-hole.  They will
>sign anything (theoretically) if it has the export
>papers and all.  Or without, if you affadavit it is not
>for export.
>
>They do not themselves impose any restrictions on crypto
>strength.
>I'm not expressing political position here, just conveying facts ....

What if the software involved was IMPORTED?  Moreover, is legal to export 
just the signature?

Jim Bell
jimbell@pacifier.com





Thread