Be patient if I'm heading the wrong way, I'm battling with the
I'm using CE5.0, with native code Apps under VS2008 - I thought it would
be a good idea to add a little bit of 'confidence' that the .exe my
users were running really is one I want them to run rather than a
corrupted file or an interim test release. My idea is to "Authenticode
sign" official releases. If that is a bad idea, do tell me!
All I want to do is test, from within my app, when it runs, whether it
is a valid, "signed" release.
I think I understand how to do that in a Win32 app, as per Microsoft KB
article http://www.yqcomputer.com/ "How to get information
from Authenticode Signed Executables". But it uses functions like
CryptQueryObject which I can't find in CE5.0.
I don't want to force all applications to be digitally signed, ie I'm
not trying to implement a "Trusted environment Model" as per
Is there a way of doing what I'm trying to do? Or an alternative way?
Any pointers to appropriate documentation would be welcome.