Patch Signing

[NickT]

I have been in contact with technical support about an issue I have when I sign Visual Patch files

The support person suggested I use Microsoft's Authenticode SDK to apply my digital signature to my patch files. However, after these files have been signed, they no longer run - the log file shows an error (Archive integrity check (20)). It seems to me that there is some internal error checking formula that is being broken when the digital signature is appended to the patch file.

I was just wondering if anyone had figured out a workaround for this problem (like a way to 'unsigned' a file??) or if there was anything else I can do besides waiting for version 2.0.1.0.
The parameters for the solution are that it has to be transparent to the user (expect for approving the digital signature), and the actual patch file needs to be digitally signed.

Thanks :)

[Brett]

I doubt if there is a way around it right now. However, we will be working on the Visual Patch update soon.

[NickT]

Thanks for the reply Brett. I am looking forward to 2.0.1!!
In the mean time, I have come up with this work around:

After I create the patch file, I add it to a zip file.
Next, I convert the zip file into a self-extracting & self-installing exe file (I am using ChilKat Software's "Zip 2 Secure Exe" program).
Then, I add a digital signature to this file.
Finally, I place this signed exe file in the location the update script will look for it.

In this way, the patch is not modified at all, instead, a signature is being added to a container around the patch.

I hope this information can help other people.

[Brett]

2.0.1.0 is now available and fixes this problem.

[NickT]

Thanks so much for the patch - that solved my problems!