EV Code Signing

[coryosborn]

I'd like to sign my executable, but when doing so, the exe no longer runs. With 1.3.15, it exits with "FATAL ERROR: Bad signature in executable.", in 1.3.17, it gives a similar message on missing signature. This is despite no using --no-lzma flags. Is there a way to alter the stub program so that the packed files can still be found after ev signing?

[shinokaro]

Thanks for the report.

At the moment, the OCRAN stub assumes that the executable image is not modified after it is built. When a code signing tool adds an Authenticode signature, the layout of the file changes and the stub can no longer reliably locate the packed payload, which results in the “Bad signature in executable” / “missing signature” fatal error you’re seeing.

So this is currently a limitation of the stub rather than something you can fix with flags. Proper support for running after code signing will require changes to the stub and some careful testing, and I’m not able to promise a timeline for that right now. I’ll keep this issue open to track making OCRAN-generated executables compatible with standard Windows code signing as a future improvement.