I was able to adapt the Setup Factory code signing to using SSL.com eSign Cloud Key Adapter.
But I am running into issues with True Update, which has not seen updates in years!
I tried using a codesign_helper.bat approach suggested in another post by Ulrich and used it to look at all the arguments being fed, but none of them had the actual target TrueUpdateClient.exe or its temporary location.
Using post-process signing is going to run into issues since it is not clear what compression or other processing is used for TrueUpdateClient.dat, which is likely a processed copy of the signed TrueUpdateClient.exe.
--- Later --
Just looked at the DAT file and it looks like a zip archive of some sort. According to the Help docs, the ts3 file is a copy of the exe, but its format is not clear.
Is TrueUpateClinet.exe the only file that needs codesigning?
But I am running into issues with True Update, which has not seen updates in years!
I tried using a codesign_helper.bat approach suggested in another post by Ulrich and used it to look at all the arguments being fed, but none of them had the actual target TrueUpdateClient.exe or its temporary location.
Using post-process signing is going to run into issues since it is not clear what compression or other processing is used for TrueUpdateClient.dat, which is likely a processed copy of the signed TrueUpdateClient.exe.
--- Later --
Just looked at the DAT file and it looks like a zip archive of some sort. According to the Help docs, the ts3 file is a copy of the exe, but its format is not clear.
Is TrueUpateClinet.exe the only file that needs codesigning?