Howe to prevent Windows mobile "unknown publisher"

Cheers for that alexey_gusev

>>you can alter Security Policy on PDA
Do you know how on top of your head? or do I have to google?

Since the app is in Live environment with lots users already using it what is the best way to ensure these autoupdate files don't cause the pop up, that is if users do not want their devices accept every file that is not signed with a certificate?  I am not really sure about certificates.  Are there freely available certificates I can use or do I have to purchase them?

H

>>>>you can alter Security Policy on PDA
>>Do you know how on top of your head? or do I have to google?

yes, I do know it, the question is how you're doing it in live environment (operationally I mean), but my my 1st list contains exact reg key location to alter - look towards the end of the wiki page

pgnatyuk,

Let me look at these links.  The company we are building the product for is reluctant to fund certificate costs.  We are trying to get a free way of stopping these pop ups.

Alexey,

In the live environment, there is a launcher app which when launched looks for newer version of the app in the web server.  If found it will download these files and overwrite old ones before launching the main exe.  What happens is that once the main exe is launched somehow WM sees it is a new one that user didn't run before and pops up the warning

>>So when you install a cab you don't see the popup? Only when you launch the application?
YES!

So I'd try to make an own certificate, sign the exe and all dlls with it, make a cab that will include this certificate. I'd make all updates only with the cab-files also.
I don't know why, but I'm thinking about the setup.dll - it can be in the cab-file. This setup, thearetically, can watch the installation process and press Ok instead of the user - but it is, probably, a bad idea.

>>So I'd try to make an own certificate
How?

>>I'd make all updates only with the cab-files also.
Why?  My update process doesn't use cab.  What happens if I sign my update files, will that stop the pop up.

The setup.dll is not such a good idea.  The app is already installed on the devices.  It looks Like I have only "sign the update files" option left.  If you can tell me how to sign them with own certificate that would be a solution

I did.

http://msdn.microsoft.com/en-us/library/bb278107.aspx

Alexey_Gusev posted a link also: http://www.codeproject.com/KB/mobile/signcode.aspx

I think everything's decribed perfect on this blog: http://bansky.net/blog/2008/12/windows-mobile-certificates-and-applications-signing/

if your app is already running on the mobile device then in the next update you can add the code that changes the registry - once and all :)

so you won't see any popups in the future except this last time.

and as pgnatyuk pointed out in prev post, http://www.codeproject.com/KB/mobile/signcode.aspx explains how to create your own certificate AND deploy it.

Thank you both.

I think I have to read these links and come back when done.  Bear with me please

H

just be aware of the fact vendors can enforce certificate policies to be inherited from 'trusted' CAs, so on some devices self-signed certificates may not work

Thanks Alexey,

I'll bear that in mind

This Q is not abandoned.  I need a bit of time.  Urgent work before I can evaluate suggestions.  Please bear with me

H

Sorry Bob,

Got sidetracked with work.  Customer opted for leaving this issue open for now.  I'll split points and apologise for leaving this open too long.

H