Re: CryptAqcuireContext logn delays
From: Ryan Menezes [MSFT] (ryanmen_at_online.microsoft.com)
Date: 04/06/04
- Next message: Ryan Menezes [MSFT]: "Re: Debug CSP"
- Previous message: Ryan Menezes [MSFT]: "Re: can't use own CSP"
- In reply to: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Next in thread: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Reply: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 6 Apr 2004 12:41:33 -0700
For W2K and beyond keys are maintained under the userprofile at
%userprofile%\Application Data\Microsoft\Crypto\RSA\<userSID>\* ,and
%userprofile%\Application Data\Microsoft\Crypto\DSS\<userSID>\*
Hard to tell why it would happen all of a sudden. Does this occur for local,
domain or roaming accounts ?
-- Thanks, Ryan Menezes [MS] This posting is provided "AS IS" with no warranties, and confers no rights. "George Nentidis" <gnentid@msn.com> wrote in message news:uvcBnt6GEHA.3068@TK2MSFTNGP11.phx.gbl... > > Thanx Ryan! CRYPT_VERIFYCONTEXT did the job. > This means that I have a large number of persisted keys on my system? > How can I check this out? And why did this happen so suddenly in 80% of my > installations? > Anyway, thanks again... > > "Ryan Menezes [MSFT]" <ryanmen@online.microsoft.com> wrote in message > news:eDSAWa5GEHA.740@tk2msftngp13.phx.gbl... > > Which platform are we talking about ? Do you have a large number of > > persisted keys on your system. ? > > > > If you dont need access to private keys, consider using the > > CRYPT_VERIFYCONTEXT flag. > > > > -- > > Thanks, > > Ryan Menezes [MS] > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > > > "George Nentidis" <gnentid@msn.com> wrote in message > > news:OL0rTRxGEHA.2768@tk2msftngp13.phx.gbl... > > > > > > Hi there All > > > > > > All of a sadden, my encryption and hashing routines became terribly > slow, > > > without changing a single line of code. > > > > > > After enough profiling, I found out that the CryptAcquireContect API > call > > > > > > which I called in each of my routines, was considerably slow. About a > sec. > > > long. > > > > > > The same thing happened in many of applications that use this API call. > > > > > > All of a sadden I hear complains of how slow it suddenly became. > > > > > > > > > > > > Could it be that any patch or service pack has to do anything with that? > > > > > > No viruses are present at the system. > > > > > > Anybody seen anything like that? > > > > > > > > > > > > Thank you all in advance > > > > > > George Nentidis > > > > > > > > > > > > > > >
- Next message: Ryan Menezes [MSFT]: "Re: Debug CSP"
- Previous message: Ryan Menezes [MSFT]: "Re: can't use own CSP"
- In reply to: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Next in thread: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Reply: George Nentidis: "Re: CryptAqcuireContext logn delays"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]