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

Header Data

From: Marc Horowitz <marc@cygnus.com>
To: roy@scytale.com
Message Hash: 0257d8528a5df2d5502fa9af5cae8b0e3c107cde9321608a319b063d3b984cc5
Message ID: <t53u3pkpehe.fsf@rover.cygnus.com>
Reply To: <961217.193402.3q9.rnr.w165w@sendai.scytale.com>
UTC Datetime: 1996-12-18 06:14:14 UTC
Raw Date: Tue, 17 Dec 1996 22:14:14 -0800 (PST)

Raw message

From: Marc Horowitz <marc@cygnus.com>
Date: Tue, 17 Dec 1996 22:14:14 -0800 (PST)
To: roy@scytale.com
Subject: Re: [NOT NOISE] Microsoft Crypto Service Provider API
In-Reply-To: <961217.193402.3q9.rnr.w165w@sendai.scytale.com>
Message-ID: <t53u3pkpehe.fsf@rover.cygnus.com>
MIME-Version: 1.0
Content-Type: text/plain


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





Thread