Re: [WiX-users] Issues signing the engine in the bootstrapper
Ok, I found out that there was an error in the build script - the signing process was being executed twice. The insignia does not handle the extraction of already signed engine well and the behavior is the result of it. After removing the certificate from the extracted engine.exe, the values in the burn section of this engine.exe are left as they were. After signing the engine and reattaching it back to the bundle everything seems fine. But when installing, the bootstrapper expects that those values were zero before signing, so it zeroes them out and breaks the signature of the engine.exe. That's it. PePri -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-signing-the-engine-in-the-bootstrapper-tp7595376p7595418.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Issues signing the engine in the bootstrapper
Seems like a reasonable thing to open a bug against Insignia to handle better, if possible. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Peter Prikryl [mailto:peto.prik...@gmail.com] Sent: Monday, June 23, 2014 12:06 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Issues signing the engine in the bootstrapper Ok, I found out that there was an error in the build script - the signing process was being executed twice. The insignia does not handle the extraction of already signed engine well and the behavior is the result of it. After removing the certificate from the extracted engine.exe, the values in the burn section of this engine.exe are left as they were. After signing the engine and reattaching it back to the bundle everything seems fine. But when installing, the bootstrapper expects that those values were zero before signing, so it zeroes them out and breaks the signature of the engine.exe. That's it. PePri -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-signing-the-engine-in-the-bootstrapper-tp7595376p7595418.html Sent from the wix-users mailing list archive at Nabble.com. -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Issues signing the engine in the bootstrapper
Hello Wix users! I am trying to create a signed bootstrapper. I found that I need to also sign the engine that is in the bootstrapper. I am using command line to build the installer (so no wixproj). I followed the steps I found in the documentation, but I still cannot inscribe the engine properly. The resulting bootstrapper works fine, but the publisher in the UAC dialog is set to unknown. I tried with both insignia 3.8.1128.0 and 3.9.616.0. At first, I extract the engine and try to sign it. The signtool says that the engine is not a valid Windows application, so I remove the certificate from the engine and try to sign it again. This time the signing finishes successfully. I can verify that the engine.exe is signed correctly. Then, I reattach the engine back to the bundle and finally sign my bundle. When running the installer, the boostrapper extracts the engine into temporary directory and runs it. This is when the UAC dialog shows the unknown publisher. I can see that the extracted engine is indeed not signed correctly (digital signature of the object did not verify). There is difference between the engine I have reattached and the engine extracted by the bootstrapper - 12 bytes are zeroed out. How can I sign the bundle correctly? Is this bug in insignia or am I doing something wrong? Thanks In Advance PePri -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing Easy Data Exploration http://p.sf.net/sfu/hpccsystems ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
