RE: How to install and test custom CSP

Thanks for comments.

I'll challenge to clear this problems...
If anyone knows how to test un-signed CSP(details), please give advice.

Thanks,
hamilton

"lelteto" wrote:

I am not familiar with WinDbg's kernel mode but I think you cannot run it on
the SAME machine as the kernel debugger is running. That's why I am always
using SoftICE instead (it can debug on SAME computer). As I remember
Microsoft's kernel debugging requires two computers: one is the debuggee (on
which the kernel debugger is running) and another connected where you control
the debugger.

Hope somebody will give you more info on how to load the kernel debugger on
the computer you want to test your CSP.

Laszlo Elteto
SafeNet, Inc.

"hamilton" wrote:

Tnanks for comment.

I tried to load KERNEL DEBUGGER on local machine.
But return value is same,"NTE_BAD_SIGNATURE"

I'm not sure that KERNEL DEBUGGER is runnning successfully or not...
Does KERNEL DEBUGGER is loaded mean starting WinDbg kernel Debug mode?
Start log is shown below, please give me some coments...

----
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.

Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Symbol search path is:
SRV*c:/symbols*http://msdl.microsoft.com/download/symbols;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050622-1524
Kernel base = 0x804d9000 PsLoadedModuleList = 0x8055e700
Debug session time: Fri Apr 7 19:24:33.593 2006 (GMT+9)
System Uptime: 0 days 0:01:28.300
lkd>
---------

And I want to try another way, "advapi32.dll" is changed, but cannot find
out "advapi32.dll" which does not check sign...
Please tell advapi32.dll patch for XP sp2(latest version).

Thanks,
hamilton


"lelteto" wrote:

Microsoft changed how test CSPs are used. Instead of test-signing now you
will need to load a KERNEL DEBUGGER on the test computer. (You don't need to
actually use the debugger - it just has to be loaded.)

Alternatively, you would need a patched advapi32.dll (which doesn't check
for the kernel debugger). Please search for this forum with the keyword
"advapi32" and you can find several patch instructions for various Windows
versions.

Laszlo Elteto
SafeNet, Inc.

"hamilton" wrote:

Hello,
I'm writing a custom CSP based on cspdk, and sign mycsp.dll as following
method.

"cspSign c mycsp.dll"

After that, I veryfy it and install on target WinXP machine.

"cspSign v mycsp.dll"
"regsvr32 mycsp.dll"

It seems to success, because there is no error and I can see my csp in
registry editor, path=....../Defaults/Provider.
But, I cannot call my csp from test code,because error is occured,
"NTE_BAD_SIGNATURE".

Please help and tell how to install custom csp and check it.

Thanks,
hamilton



.

Relevant Pages

  • RE: How to install and test custom CSP
    ... I use WinDbg's kernel mode on two computers, host and target, ... and I can use un-signed CSP on target computer. ... "hamilton" wrote: ... the SAME machine as the kernel debugger is running. ...
    (microsoft.public.platformsdk.security)
  • RE: How to install and test custom CSP
    ... I am not familiar with WinDbg's kernel mode but I think you cannot run it on ... the SAME machine as the kernel debugger is running. ... "hamilton" wrote: ... I'm writing a custom CSP based on cspdk, ...
    (microsoft.public.platformsdk.security)
  • Re: Coredll patch Windows CE 4.21
    ... you first create a Windows CE project based on the ARM emulator. ... Debugging a CSP is similar to debugging ... windows ce images/apps using platform builder and arm emulator. ... > the platform builder and activating the flag "Enable Kernel Debugger" ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How to connect to the target system to debug CSP
    ... Have you configured the Kernel Debugger on the other machine? ... then set Baud rate and COM port and then restart the other machine. ... > of my CSP or CSP test suite). ... > I have set the communication between both systems and both are XP SP1. ...
    (microsoft.public.platformsdk.security)
  • Re: advapi32.dll patch for Win2003 SP1
    ... You don't have to actually USE the Kernel debugger - you are free to use your ... be LOADED in order to allow your CSP be used by the system. ... > to use the kernel debugger when I test unsigned CSPs. ...
    (microsoft.public.platformsdk.security)