NewsArchive
09-08-2009, 01:30 AM
Code signing of the setup seems bulletproof.
But I have had some issues with code signing my own .exe and .dll.
Today I found a real sly way to make it fail:
You setup the codesigning, but do NOT add a TimeStamp
Compiles, and your .exe is codesigned.
Then you add the timestamp, and compiles again.
ERROR
This is what i call an error 45 - I am slightly overweigt. Error 65 is an
error 40 for fat persons...
I think I have done so several times, and I am afraid that I have used some
of Friedrichs costly time on it.
I know i should shift to SB7, where the timestamp is a drop down instead.
Humble regards
Edvard Korsbćk
But I have had some issues with code signing my own .exe and .dll.
Today I found a real sly way to make it fail:
You setup the codesigning, but do NOT add a TimeStamp
Compiles, and your .exe is codesigned.
Then you add the timestamp, and compiles again.
ERROR
This is what i call an error 45 - I am slightly overweigt. Error 65 is an
error 40 for fat persons...
I think I have done so several times, and I am afraid that I have used some
of Friedrichs costly time on it.
I know i should shift to SB7, where the timestamp is a drop down instead.
Humble regards
Edvard Korsbćk