From: Matthew James Sheppard <Matthew.Sheppard@Comp.VUW.AC.NZ>
To: cypherpunks@toad.com
Message Hash: ceef595302cf6fa100f9e821f4321089556812f0ea2eee3b8bd45912111415e7
Message ID: <199601180110.OAA12788@bats.comp.vuw.ac.nz>
Reply To: <pxT/w8m9LAcF085yn@netcom.com>
UTC Datetime: 1996-01-18 09:09:51 UTC
Raw Date: Thu, 18 Jan 1996 17:09:51 +0800
From: Matthew James Sheppard <Matthew.Sheppard@Comp.VUW.AC.NZ>
Date: Thu, 18 Jan 1996 17:09:51 +0800
To: cypherpunks@toad.com
Subject: Re: Microsoft's CAPI
In-Reply-To: <pxT/w8m9LAcF085yn@netcom.com>
Message-ID: <199601180110.OAA12788@bats.comp.vuw.ac.nz>
MIME-Version: 1.0
Content-Type: text/plain
The shadowy figure took form and announced "I am Alan Bostick and I say ...
> The next obvious question is: Will Microsoft sign strong-crypto CSPs
> developed by foreign developers for out-of-USA use?
To obvious really, if they signed strong foreign crypto MS would
neither be exporting strong crypto or exporting an application that
had general purpose crypto hooks, since technically only that specific
foreign implementation could be used.
However I would guess that the arrangement with the guvmint would
label the signing to be the equivalent of MS exporting an application
with strong crypto and subject to the same disciplinary measures, just
transfered to the time of signing. Perhaps there will be some
modification to the itar - thou shalt not _enable_ foreign markets to
have strong crypto.
I assume MS would be free to sign weak foreign crypto, but as "weak"
crypto is hard/expensive to determine I think they would take the easy
way out. Id also expect a kernel patch to be part of the install
procedure of foreign crypto.
--Matt
Return to January 1996
Return to “scox@factset.com (Sean Cox)”