Eclipse Community Forums: Oomph » Custom Oomph binary

Home » Eclipse Projects » Oomph » Custom Oomph binary - Windows signing(Signing error 0x800700C1)

Custom Oomph binary - Windows signing [message #1767447]

Thu, 06 July 2017 04:02

Eclipse User

(cross-post from mailinglist)
Hi,

first of all, let me tell you how awesome Oomph is! It really makes
consuming Eclipse far more convenient than before. It's a pleasure to
use, even compared to our previous way of inhouse Eclipse delivery
(based on Java Webstart + some property file editing ;) + Workspace
mechanics + custom provisioning plugin - though all of that worked way
better than it sounds written down).

Now, we are trying to build the binaries ourselves to point them to our
own catalogue. This works great but the resulting binary cannot be
signed by the Windows signtool.exe. I tried using the official Oomph
binary and I was able to resign it without issues. Our own binary
unfortunately produces an "SignTool Error: SignedCode::Sign returned
error: 0x800700C1 - %1 is not a valid win-32 application".

Now the question: Besides concatenating the binaries (extractor, product
zip, markers, etc) - do you during the build process (or sign process)
any modifications to the exe which we are missing? Any help would be
greatly appreciated!

Greetings
-Sascha-

Re: Custom Oomph binary - Windows signing [message #1767466 is a reply to message #1767447]

Thu, 06 July 2017 05:13

Eclipse User

I guess you already looked at https://wiki.eclipse.org/Eclipse_Oomph_Authoring#How_to_extract_the_constituent_parts_that_comprise_the_Windows_self-extracting_installer_executable for how to get at the parts that you need to create your own *.exe. You can see we use this approach to massage the *.ini using /org.eclipse.oomph.releng/hudson/repackage.sh and it does nothing special to prepare the *.exe for signing. Does the unsigned *.exe you produce run (suggesting that it is a well-formed win-32 application)?

Re: Custom Oomph binary - Windows signing [message #1767467 is a reply to message #1767466]

Thu, 06 July 2017 05:20

Eclipse User

Hi, yes I did and even when I just extracted the official Oxygen Oomph exe and repackaged it I was no longer able to sign it. As said, resigning of the plain Oxygen installer works (and Windows file properties now lists my cert in the signing details instead of Eclipse's cert).
Despite the nasty "you have an unsigned installer"-dialog both, my exe and the repackaged Oxygen exe work fine (loading our custom setup catalog, or the Oxygen one loading the official catalog).

Thanks for the link to the repackage.sh - I will have a look at it too to see if I find anything in there.

Any more insights are greatly appreciated :) and thanks in advance!

Re: Custom Oomph binary - Windows signing [message #1767485 is a reply to message #1767467]

Thu, 06 July 2017 06:59

Eclipse User

That's odd. You'll see the script does curl -o signed.exe -F filedata=@eclipse-inst.exe http://build.eclipse.org:31338/winsign.php so we use Eclipse's signing service, but I have no idea how that's implemented under the covers.

Previous Topic:	Oomph setup for Oxygen. Help needed.
Next Topic:	problems in the eclipse installation: failed

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 15 20:10:49 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter