Re: How to deploy real cert in packaged .exe (VS 2005, .net cf 2.0 sp2, WM 5.0)

To achieve no prompts on installation your package has to be signed with a certificate already installed on the device. You have two options - sign your app and cab file with a Mobile2Market certificate e.g. through VeriSign, or create a cab file specifically to deploy your own certificate(s) and have this signed with a Mobile2Market certificate - once this has installed your own certificate correctly you can then deploy your own application which is self signed.
The certificate vendors have been making the process easier, you can now sign an entire cab file and all its contents in a single signing event, previously each .exe and .dll within the cab would require its own signing event.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
peterfoot.net | appamundi.com | inthehand.com
APPA Mundi Ltd - Software Solutions for a Mobile World
In The Hand Ltd - .NET Components for Mobility

"Jin Chang" <jinsoochang@xxxxxxxxx> wrote in message news:5e378545-f155-455d-bc51-15093fefe423@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 20, 2:59 pm, NET CF Questions <dotnetcfquesti...@xxxxxxxxx>
wrote:
We are developing an application for a Windows Mobile 5.0 device using
VS 2005, .net cf 2.0 and currently when we deploy it to the device for
testing we get the following error;
"The program is from an unknown publisher ...(etc)"

When we go to package this for real use (not test), what are the steps
we need to follow so this warning doesn't appear on the device?

I have seen the instructions here:http://ce4all.blogspot.com/2007/04/siging-windows-mobile-application-...

but is that for the real environment or just the test environment?

What certs and signings do I need to include how (the steps in VS 2005
please) to do this for a real app?

I would like to bump this thread with an added question/issue.

First of all, there are plenty of information on the web and this
forum about certificates and code-signing, but the problem I'm facing
are the following:

1. Why is it so difficult to use chained certificate for code-signing
with WM devices? One of the source I ran across mentions that it's an
issue with WM 5 and 6. Can someone confirm this so that I might get a
more appropriate certificate?

2. How in the world can one sign a CAB file so that the certificate
is also deployed in one step without the "unknown publisher" message
being displayed? Is it a catch-22 situation where the certificate
must be installed before the CAB can be run without the warning?

I must have read at least 20 different sources on this topic and the
solution still eludes me. Why can't WM code-signing be as easy as
it's for normal PC's OS? Are there reasons why the Cert Vendors make
it so difficult or are WM devices not quite ready-for-prime-time for
these processes to be in place?

- Jin

.

Relevant Pages

  • Signing drivers with signtool for XP 64-bit -- suppressing the war
    ... Ineed to suppress the unsigned driver installation dialog for an automation ... article "Driver signing policy is automatically elevated for unsigned ... I need to sign our drivers for unattended installation via ... Signing Certificate Chain: ...
    (microsoft.public.development.device.drivers)
  • Re: DIFx Framework - HOWTO
    ... The certificate was not installed on the machine, that's s why I did exactly ... The test certificate is obtained through the commands: ... I've successfully created the unsinged cat file using: ... >> installation through DIFx framework but have some troubles with it. ...
    (microsoft.public.development.device.drivers)
  • Re: client installation error
    ... The certificate is TRUST_E_TIME_STAMP however I do not think that will help. ... This posting is provided "AS IS" with no warranties, ... the installation stop at this error "Error 0x80096005: ... >> Jeff Harbaugh [MSFT] ...
    (microsoft.public.sms.setup)
  • Re: Dear "Well Known National Alarm Company":
    ... I believe it 's only until recent years that a dedicated circuit is required for the communicator. ... certificate was issued in 2006 and should be valid until 2011. ... The first "inspection" was signed off one month after installation. ... ULC requires that you monitor the supervisory output. ...
    (alt.security.alarms)
  • Re: recovering files encrypted using EFS
    ... > same name and password as the old WinXP installation, ... > intact backup of the old harddisk on COMP2, ... > didn't export the EFS certificate, ... I could of course restore ...
    (microsoft.public.windowsxp.security_admin)
Loading