NewsArchive
09-11-2015, 09:40 AM
While trying to test my new comodo certificate using sha-2, I found interesting
situation (with sha-1 pragma all works ok).
Whichever one from the newer signcode.exe I use, and whichever one timestamp
server I use, I get a message about "signcode.exe stopped working".
I can fool SetupBuilder to continue compliling anyway, but final result is
weird, I get codesigned exe without "timestamp".
And "codesign verify /pa" says that's all OK with codesign.
Anyone has similar experience? I am doing all testing on win 7/x64
Plus, besides my main problem about what's happening here, I would expect SB
should not compile fine with SHA-2: 0 result.
Thanks for any idea
Darko
situation (with sha-1 pragma all works ok).
Whichever one from the newer signcode.exe I use, and whichever one timestamp
server I use, I get a message about "signcode.exe stopped working".
I can fool SetupBuilder to continue compliling anyway, but final result is
weird, I get codesigned exe without "timestamp".
And "codesign verify /pa" says that's all OK with codesign.
Anyone has similar experience? I am doing all testing on win 7/x64
Plus, besides my main problem about what's happening here, I would expect SB
should not compile fine with SHA-2: 0 result.
Thanks for any idea
Darko