views:

84

answers:

2

I purchased a code signing certificate and all looks well. When tested inside a clean Virtual PC OS I no longer get the "The Publisher could not be verified" message.

So just for grins, using a hex editor, I change a few constants in the VB6 exe which I see on a form. And the VB 6 exe still runs wihout any error message.

I thought the code signing certificate would tell you if the file had been changed in any way?

+1  A: 

Yes, Authenticode will indicate that the signature is invalid if the file is modified.

However, running a program from your local disk won't typically check the signature; right-click on the EXE, choose Properties and choose Digital Signatures to see a signature error message.

EricLaw -MSFT-
Yes, that worked. Interesting. However what concerns me is the screen displayed when the exe has been tampered with. It states "The publisher could not be verified" and is identical to the regular message received when the exe hasn't been signed at all. This concerns me as a tampered exe should have a much bolder message stating "tampered". As well as sirens going off and a blinking/rotating red light.
Tony Toews
Also the message displayed when I did choose Digital Signatures on my own system was quite boring. All it said was something like invalid digital certificate with a tiny red X.
Tony Toews
+1  A: 

If an evil-doer can gain enough access to your machine to change bytes in a file then you are already pwnded. The Signature is there mainly to verify files before you install them. You could of course write your own program to scan your files and recheck their signatures for trust, but the evildoer would just change the bytes in your scanner as well.

Jim In Texas