Hello
Having a little trouble with some drivers from FTDI that I’ve got signed for our custom VID/PID. I’ve jumped through all the correct hoops (Verisign certificate, Microsoft DUA) but on some PCs the device gives Error 52 in Device Manager claiming that the signature cannot be verified. (Screenshot: http://db.tt/fsvFGYAh)
Everything else looks fine (http://db.tt/B9PoupI0)
I signed the cat files using SignTool with my certificate and the primary cross certificate found here: http://www.verisign.com/support/verisign-intermediate-ca/code-signing-intermediate/index.html
My process was: SignTool sign /f /p /t http://timestamp.verisign.com/scripts/timstamp.dll /ac /v
I then used SignTool verify and all looked ok: http://db.tt/08L6kaON
Anyone got any ideas? Symantec were no help and just told me the cat file was either not signed, or corrupt, but didn’t say how.
Thanks
Ben