Re: Debugging CSP

From: Adam Augustyn (gustaw_at_isonar.com.pl)
Date: 02/28/05 

Date: Mon, 28 Feb 2005 12:49:59 +0100

WT wrote:
> I am testing my CSP and set it to be type 001 default. The problem is that I
> can't copy a new CSP over the existing one (in windows\system32) since the
> DLL is loaded. Each time I change/update my CSP, I have to switch back in
> the MS base CSP in the registry, reboot, copy over my new CSP, re-assign my
> CSP to be type 001 default and reboot again.Is there a way to unload and
> reload a DLL so as to allow replacement of the DLL file?
> WT

The main problem is connected with Winlogon - it keeps CSP loaded all
the time. There is a method to test as many builds as you want without
reboots. You can change the name of CSP file locked by Winlogon and next
copy new dll image into system32 directory. After that the new CSP file
will be loaded for requesting applications. Of course this workaround
will not work for testing CSP with Winlogon. It still will be requiring
reboots :(.

Gustaw

Relevant Pages

  • RE: Debugging a CSP dll
    ... you are registring your CSP the right way. ... it's not sufficient for winlogon to load it. ... Actually, by default, Winlogon ... dll unless it appears as a PC/SC reader to the system, ...
    (microsoft.public.platformsdk.security)
  • RE: MSCAPI integrity checks of CSPs - Downgrade Attack
    ... One thing you can do is to go to the Registry, ... the CSP dll file name from the crypto provider entry the VERIFY the dll ... the advapi32.dll file to completely bypass CSP signature check so can install ... I configure certificate server templates or xenroll to only issue ...
    (microsoft.public.platformsdk.security)
  • Re: CSP error
    ... You get the dll name from the Registry ... This behavior have some security risks because you load a potentially ... "unknown" CSP which may or may not signed by Microsoft. ... > am trying to do it is to call back to the Crypto level which is not a very ...
    (microsoft.public.platformsdk.security)
  • Re: CSP types
    ... You can write one dll and expose/register it via different types of CSPs. ... > I can write one CSP and one DLL and declare my self as supporting a few> CSP ... >> So on Windows 95 and Windows NT 4.0, there's a one-to-one mapping between>> CSPs and DLLs. ... one DLL can support any number of CSPs and>> types. ...
    (microsoft.public.platformsdk.security)
  • Re: CSP types
    ... You'll probably end up using the same entry points within ... specific to the CSP selected, as most of the code will be the same for all ... Note that each CSP supported by the DLL must have a separate unique name. ... >> On Windows 98, one DLL can support multiple CSPs, as long as each CSP is ...
    (microsoft.public.platformsdk.security)