-----BEGIN PGP SIGNED MESSAGE-----
At 07:00 30-12-97 -0600, William H. Geiger III wrote:
My understanding is that the MS Crypto API that is shiped overseas
contains only weak crypto. The API is also signed so that no new/modified
code can be added without the MS signature.
I don't know for sure but I would imagine that the export product makes
use of a different key then the domestic product so that the domestic code
will not run on the export version.
The way I understand it, the API requires that the crypto module be signed
with Microsoft's corporate key. I assume that Microsoft follows ITAR in
deciding which modules get signed. The USG required such a mechanism before
allowing export of Microsoft products that include the API. For the
purposes of this working group, that makes it useless.
--
Anthony E. Greene <agreene(_at_)pobox(_dot_)com>
PGP Key: <http://www.pobox.com/~agreene/pgp/agreene.key>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv
iQCdAwUBNKlA+0RUP9V4zUMpAQHrcgQ6AhR0Y25/dEVLvmujkaSbNg6kPo6sCxqa
b0BvCoiljle6PdsYfBxvIkUMhvF7/EuchqWaaU9tQysO5qhEJuBc0xVli2Mxv8Oa
azlBSlF69V7D87oDhzuXDsab5Z7F4UpoN6nD0fSW6LybfLc7wunEsdynCI6Kei3d
A66ZNSJeESJ1vX1WzjPpGA==
=PQcr
-----END PGP SIGNATURE-----