Greg
Mon May 05 10:44:19 CDT 2008
I'm sure the blob was encoded by WinCE 5.0 as it saw fit, but our customers
are only using one model of the device: Symbol (Motorola) MC3000 Series
running WinCE 5.0... So that won't be an issue.
No one could provide me with a way to package the certificate into a Visual
Studio 2005 project, nor would anyone offer suggestions on how to configure
an information file (*.inf) in order for cabwiz to build the cab file
correctly, so doing it the way I did was my only option. When the
certificate expires and has to be renewed or If we ever do go to another
type of os/device then I'll have to perform the procedures all over again
anyhow.
- Greg
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:%23pFmF2kqIHA.4476@TK2MSFTNGP04.phx.gbl...
> Make sure you test with another device! The encoding of that blob might
> easily be device-specific.
>
> Paul T.
>
> "Greg Hellem" <ghellem@airmail.net> wrote in message
> news:b_mdnf2SB66QG4rVnZ2dnUVZ_hCdnZ2d@internetamerica...
>> Oh well, I figured it out for myself!!
>> In order to get the SSL Certificate installed programmatically (via CAB)
>> on the mobile device I had to perform the following:
>> 1) Performed a Cold Boot (Hard Reset) on the mobile device to get
>> everything back to factory defaults.
>> 2) Used Remote Registry Editor (VS 2005) and exported the device's
>> Windows Registry to my desktop.
>> 3) Manually installed the SSL Certificate on device.
>> 4) Again, exported the device's registry.
>> 5) Compared both exported registries to see what keys were
>> added/modified.
>> 6) Copied the "Blob" registry key (hex values separated by commas) and
>> removed all line ending "\" characters as well as all new-line characters
>> from the string.
>> 7) Created an Information File (.inf for cabwiz.exe) and used the AddReg
>> statement to add the appropriate registry data containing the hex
>> conversion (from step 5) of the SSL Certificate and packaged it all into
>> a WinCE CAB file!
>> 8) Copied the CAB to the device and then installed it, from the device
>> UI, examined the Control Panel > Certificates and all is now right with
>> the world.
>> <end-of-message>
>>
>> "Greg Hellem" <ghellem@airmail.net> wrote in message
>> news:C5qdnbIRm8ODZ4jVnZ2dnUVZ_rignZ2d@internetamerica...
>>>I am attempting to install a SSL Certificate on a WinCE 5.0 mobile
>>>device. I have already created the appropriate "_setup.xml" file that
>>>contains the SSL Certificate installation information (as shown in
>>>several posts/blogs/WinCE32 SDK). Now I am attempting to package
>>>_setup.xml (or just it's contents) into a valid WinCE 5.0 CAB file. Using
>>>the makecab utility provided in the WinCE32 SDK, as in: "makecab
>>>_setup.xml rootcert.cab" does not create a "Valid Windows CE Setup File",
>>>as reported by the WinCE device when I attempt to manually install the
>>>CAB. Therefore it seems like I must somehow utilize the "cabwiz.exe"
>>>program, that also comes with the SDK, to try and package my _setup.xml,
>>>but how? I have no "Application" to install so what would I specify in
>>>the ".inf" file???
>>>
>>> Questions:
>>> 1) When running cabwiz.exe (WinCE 5.0 SDK), how do I package my
>>> "_setup.xml" using a ".inf" file when there is no application to
>>> install?
>>> And/Or...
>>> 2) How do I determine if "_setup.xml" must be considered as extra
>>> information for "_setup.xml", which apparently the file that cabwiz.exe
>>> itself creates inside of the new cab file!??
>>>
>>> The command-line for cabwiz.exe offers the /prexml or /postxml options
>>> when creating a cab file - do I need to use them or do I somehow
>>> indicate, within the ".inf" file, that my "_setup.xml" file is input for
>>> the cab build? I guess I'm just not sure on how to create the ".inf"
>>> file for cabwiz without really having an application to install and then
>>> go about the task of indicating to the cab setup, "Oh, by the way, would
>>> you mind running this snippet of xml contained in my '_setup.xml' file
>>> so the appropriate SSL Cert Info is imported/registered properly?"
>>>
>>> I really hope I'm not confusing everyone but I could certainly use some
>>> clarification on how I can package the SSL Certificate '_setup.xml'
>>> (mentioned in several blogs/posts that I've seen for PocketPC and
>>> Windows Mobile 5/6) into a valid WinCE 5.0 Cab file that I require for
>>> my Symbol/Motorola MC3000 Series WinCE 5.0 mobile device...
>>>
>>> Thank you for your time,
>>> Greg Hellem
>>>
>>>
>>
>>
>
>