locked
Code signing fails during WinMobile build makeimg phase RRS feed

  • Question

  • When attempting to load a debug version of DLLs from the release directory via Platform Builder, I get the following message: "CertVerify: backlight.dll trust = 0" and the DLL fails to load.  I then realized that ANY DLL loaded from the release directory fails in the same manner.  It seems that if it is built into the OS image it is loaded without issue. Looking throught the makeimg.out log I found several errors when the tool tried to sign DLL files.  After researching here and on the web, I found some signing certificate files in the ...\PUBLIC\OSSVCS\OAK\SIGNKEYS directory that expired on7/30/2011.  My hunch is that these expired certiifcates are causing these errors.

    The certificates are the Privileged Signing Cert issued by Stinger Privileged Root.  The root certificates are in the same folder.  A similar set of certs are present for Unprivileged signing.

    Is there a way to update these certificates?

    I am using WinMobile 6.5.3

    Thanks!

     


    Thursday, August 4, 2011 7:09 PM

All replies

  • Yeah, that was a shocker for a few people.

    Create your own certificate and use that instead for your debug builds

    -PaulH


    Friday, August 5, 2011 12:34 AM