[NOT NOISE] Microsoft Crypto Service Provider API
-----BEGIN PGP SIGNED MESSAGE----- I just got my copy of the Microsoft Cryptographic Service Provider Development Kit, Version 1.0. It appears to support only Windows NT. A first glance reveals no built-in GAK (but I haven't examined it closely yet!). Dammit, now I'm going to have to build an NT box! - -- Roy M. Silvernail [ ] roy@scytale.com DNRC Minister Plenipotentiary of All Things Confusing, Software Division PGP Public Key fingerprint = 31 86 EC B9 DB 76 A7 54 13 0B 6A 6B CC 09 18 B6 Key available from pubkey@scytale.com -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMrdK4Rvikii9febJAQFXQQP/TUlEBwQpLNE3WBq45AXcbAzqc8RkmvkT 5mtz2FSwGleKvg5HRjB5JF3SjjyQ32nsGMpnt/J/r6K84Q7pJWPBHOPgcVzEGSqw ORqumCQlL8uUJKk552BdB9X92QNiDV33QkIIyKQv8An208jTnqEWrYvg1R1lwCXf lkne/kxf0po= =fQZX -----END PGP SIGNATURE-----
roy@sendai.scytale.com (Roy M. Silvernail) writes:
I just got my copy of the Microsoft Cryptographic Service Provider Development Kit, Version 1.0. It appears to support only Windows NT. A first glance reveals no built-in GAK (but I haven't examined it closely yet!).
You're right, you haven't looked at it closely. Although it doesn't have Key Escrow, new cryptosystems can only be added if they are signed by a private key held by Microsoft. Of course, Microsoft has agreed with the State Dept. to sign only export-"strength" crypto. Marc
participants (2)
-
Marc Horowitz -
roy＠sendai.scytale.com