Re: Coredll patch Windows CE 4.21

Yes, you first create a Windows CE project based on the ARM emulator. You
can pick the 'mobile handheld' as a base config. Kernel debugging should be
enabled by default on debug configs. Debugging a CSP is similar to debugging
any normal Windows CE application using platform builder. The online
documentation should help you with details of building/downloading/debugging
windows ce images/apps using platform builder and arm emulator.

thanks
--
Ganapathy Raman
Program Manager, Windows Mobile/CE Security
This posting is provided "AS IS" with no warranties, and confers no rights.

"Antonio Andres" <aae1@xxxxxxxxx> wrote in message
news:un5zf.55559$kp.500321@xxxxxxxxxxxxxxxxxxxxxxx
> Hello. Thanks for the answer.
>
> We are a research group with a certain experience in CSPs with x86
> architectures (Windows 2000/XP), but we are beginners in the same subject
> with pocket PC's devices.
>
> I'd want to make you some questions.
>
> The way you say to do the tests of our CSP in a Pocket PC device is using
> the platform builder and activating the flag "Enable Kernel Debugger"
> isn't it?. But I don't know what I must to do. Do I must to do a new
> Windows CE Platform using an ARM BSP from selection (for example the ARM
> Integrator ARMV4I), build the image with the flag "Enabling Kernel
> Debugging" activated and download the image built using the '4.20
> Emulator' as device (this option appears in the 'Configure Remote
> Connection' option)?. Or what I must to do?
>
> Thanks and sorry if what I'm asking doesn't have much sense, but I repeat
> we are beggining in the Platform Builder World.
>
> Regards,
> Antonio.
>
>
>
> "Ganapathy Raman (MS)" <graman@xxxxxxxxxxxxxxxxxxxx> escribió en el
> mensaje news:elSqP2uGGHA.1028@xxxxxxxxxxxxxxxxxxxxxxx
>> You dont need the patch on CE 4.2. Signature checking of the CSP is
>> disabled when the kernel debugger is attached. So you can debug your
>> unsigned CSP using platform builder.
>>
>> --
>> Ganapathy Raman
>> Program Manager, Windows Mobile/CE Security
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Antonio Andres" <aae1@xxxxxxxxx> wrote in message
>> news:ZqOyf.43740$kp.416715@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hello. First of all thanks for the answer.
>>>
>>> Well, I'll try to show exactly what I want to do.
>>>
>>> The scenario is as follows:
>>> - I have the platform Builder v4.2
>>> - I ave a Pocket PC with Windows Mobile 2003
>>> - I have a CSP developed for Windows XP which allow to use a concrete
>>> type of smartcards
>>>
>>> Now, I want to transfer the actual implementation of the CSP to be used
>>> in a Pocket PC device. The problem is that Microsoft don't allow to use
>>> a new CSP in a device if this is not signed by they, and I need to do
>>> some tests to debug my CSP before it gets sent to Microsoft for signing.
>>> The coredll patched (which I commented in my post) allows to do tests
>>> with a not signed CSP. I have an older version of this coredll patched,
>>> the v2.11, provided by Microsoft.
>>>
>>> Now the questions:
>>> 1) Is there any way to do tests with a not signed CSP in my device
>>> before it gets sent to Microsoft for signing?
>>> 2) Could I use the platform builder to do these tests?. If the answer is
>>> YES, what I must to do?
>>>
>>> Thanks in advance,
>>> Antonio.
>>>
>>>
>>> "John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx> escribió en el mensaje
>>> news:%23nkZyyHGGHA.1552@xxxxxxxxxxxxxxxxxxxxxxx
>>>> If you have contacts within Microsoft (in particular some sort of
>>>> Technical
>>>> Account Manager or whoever you're working with to get your software
>>>> signed
>>>> or general product support?) you may have better luck. I'm not
>>>> familiar
>>>> with the patch, but if such a thing is available I would hope it'd be
>>>> more
>>>> readily had from a QFE site in MS somewhere.
>>>>
>>>> Most people on this group develop to Platform Builder so they'll have
>>>> CE 4.2
>>>> and CE 5.0 bits, but not the exact coredll on the PPC 2003.
>>>>
>>>> --
>>>> John Spaith
>>>> Software Design Engineer, Windows CE
>>>> Microsoft Corporation
>>>>
>>>> Check out the new CE Networking Team Blog at
>>>> http://blogs.msdn.com/cenet/.
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>> You assume all risk for your use. © 2003 Microsoft Corporation. All
>>>> rights
>>>> reserved.
>>>>
>>>> "Antonio Andres" <aae1@xxxxxxxxx> wrote in message
>>>> news:g%wxf.4932$kp.120671@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Hi everybody.
>>>>>
>>>>> Please, could someone pass me the patch for the coredll.dll in
>>>>> windows ce v4.21 (Windows Mobile 2003 second edition) for a ARM
>>>>> archuitecture?
>>>>>
>>>>> I need to do some tests with a CSP that I've developed before it gets
>>>>> sent
>>>>> to Microsoft for signing.
>>>>>
>>>>> Thanks in advance,
>>>>> Antonio
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Coredll patch Windows CE 4.21
    ... The way you say to do the tests of our CSP in a Pocket PC device is using ... the platform builder and activating the flag "Enable Kernel Debugger" isn't ... Do I must to do a new Windows CE ...
    (microsoft.public.windowsce.platbuilder)
  • Re: debugging CSP in kernel debuggin mode
    ... The livekd utility that was shipped with Inside Windows 2000 is also ... >> You need a second computer with a serial cable attached to run a kernel ... > kernel debugger (just to avoid csp signature verification process). ...
    (microsoft.public.platformsdk.security)
  • RE: How to debug a custom CSP?
    ... In newer Windows versions that will not help, ... Windows will not load your CSP - unless a Kernel debugger is loaded on your ... > Could you shed some lights how to debug CSP dll? ...
    (microsoft.public.platformsdk.security)
  • Re: evc4.0 connet with develope board problem
    ... for Windows CE" in Transport, ... is it i not build a correct SDK? ... Make sure your platform manager connection ... Also make sure you don't run the kernel debugger on device in the same ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Should we sign DLLs used by a CSP.
    ... dlls that you use. ... wouldn't be able to just write a strong crypto CSP and add it to Windows. ... API provided via one of the CPAcquireContextparameters. ...
    (microsoft.public.platformsdk.security)