Windows Mobile application signing
UPDATE: Apparently, there is a different technology than Authenticode that I should be using for Windows Mobile.
Most of the documentation to sign code for the Windows Mobile device assumes you want to do it all through the Visual Studio enviornment. Well I don’t. Here is what you need to do to get your application signed as well as the install cab created and signed using the command line.
First, get your certificate from verisign, godaddy, or some other certificate authority. Follow their directions to install it in your store and create a *.pfx file. I used godaddy http://help.godaddy.com/article/5087.
Sign the exe using the signtool.exe
signtool sign /f {yourcert.pfx} /p {yourpassword} /t {http://yourtimeserver} {yourexe}
Second, You will need an ini file that cabwiz.exe will use to create the cab file. The easiest thing is to create a SmartDeviceCab project and use Visual Studio to determine what you will install on the device. When you compile this SmartDeviceCab project, it creates an ini file. You use this ini file to create your CAB file as your starting point. Run the following command to create the cab file:
cabwiz.exe your.inf /cpu CEDevice /compress
After you have created your cab file, you can then sign the cab file the same as you signed your EXE. That should be all there is to it.
[...] programming with passion Learning the Mac, iPhone, and Ruby development « Windows Mobile application signing [...]