From: Adamsc@io-online.com (Adamsc)
Date: Wed, 25 Dec 1996 22:09:54 -0800 (PST)
To: "cypherpunks@toad.com>
Subject: RE: [NOT NOISE] Microsoft Crypto Service Provider API
Message-ID: <19961226060647781.AAA212@localhost>
MIME-Version: 1.0
Content-Type: text/plain


On Wed, 25 Dec 1996 23:17:53 -0500, Blake Coverett wrote:

>And to think MS was good enough to provide an UpdateResource 
>API that I haven't yet had a good reason to use.

Right thoughtful of them, wasn't it..? <g>   

>> Interestingly enough, CSP signatures are held in the registry instead of
>> the binary, necessitating some install procedure for a given CSP.  Not
>> to start rumors, but NT 4.0 does use threads to watch some registry
>> entries that control the version (workstation/server).  Not much of a
>> stretch to imagine a thread that tracks (reports?) changes to
>
>Nope, a little experimentation shows you can change those entries
>while the system is running to your hearts contents.  Try temporarily
>renaming the signature key of the base provider.

Now, yes.  However I wonder how quickly a service pack would be released to
extend the monitor garbage...

#  Chris Adams  <adamsc@io-online.com> | http://www.io-online.com/adamsc/adamsc.htp
#  <cadams@acucobol.com>                 | send mail with subject "send PGPKEY"
"That's our advantage at Microsoft; we set the standards and we can change them."
   --- Karen Hargrove, Microsoft (quoted in the Feb 1993 Unix Review editorial)