On 24/01/2012 20:09, Paul Fazio wrote:
I'm trying to get bundle signing to work and I'm having some issues. I've
addedSignOutputtrue/SignOutput, as mentioned. I've also overridden
SignBundleEngine and SignBundle, which appear to be working because burn.exe
and my bundle do have digital
On 15/05/2012 11:35, Bruce Cran wrote:
I think that error occurs if you compress packages into the installer
executable but don't sign them: I found that if you sign the installer
but leave the MSI files unsigned then Burn fails to extract them at
runtime.
The problem wasn't with the
On 24-Jan-12 15:09, Paul Fazio wrote:
However, when I attempt to install I get the following error: Setup
failed while installing the MSIs. Unspecified error.
Where? The Burn log will have additional details, like an error code.
--
sig://boB
http://joyofsetup.com/
From: b...@joyofsetup.com
On 13-Jan-12 01:41, Peter Hull wrote:
Bob: would it be possible to have the burn engine signed (by Microsoft) in
the released WiX 3.6
That would mean that the UAC prompt would show Microsoft as the owner of
your bundle.
OK, I had thought the UAC prompt would
On 13-Jan-12 01:41, Peter Hull wrote:
Bob: would it be possible to have the burn engine signed (by Microsoft) in
the released WiX 3.6
That would mean that the UAC prompt would show Microsoft as the owner of
your bundle.
or have an option to specify the burn engine in the .wxs file - as I
To sign the bundle and bundle engine you need to add the following to your
.wixproj:
Add SignOutputtrue/SignOutput to a PropertyGroup
Implement the targets like this:
Target Name=SignBundleEngine
SignFile TimestampUrl=... CertificateThumbprint=...
SigningTarget=@(SignBundleEngine) /
of this discussion so far, I must sign
as part of the build process - something that will cause us a bit of an issue.
Is that right?
-Nick
-Original Message-
From: Peter Hull [mailto:peterhul...@hotmail.com]
Sent: 12 January 2012 08:58
To: WiX Users
Subject: Re: [WiX-users] Signing the burn
On 12-Jan-12 05:47, Nick Ball wrote:
I haven't started using burn yet - but I'd like to - and signing will be an
issue for us. At the moment, I hand an unsigned MSI over to the release
manager for signing. He is the only person with access to the certificate.
Can we still do this with burn?
Signing only the bundle would prove that it came from your organisation and
hadn't been tampered with - would that be enough?
When run it would unpack the unsigned burn engine and the unsigned MSIs. Does
anyone know if that would show the user a warning (or multiple warnings?)
Bob: would it be
Thanks Rob, a blog post would be great!
As I am not that familiar with modifying the MSBuild sequence, do I just
specify something like Target Name=Signing SignTargetPath=PathToMyExe/
in my wixproj?
I guess I should probably sign all my MSI's with a digital certificate using
the signtool before
There are like four Sign* targets in wix2010.targets. Create a target named
the same for each and all of your things can be signed. It's actually
really easy.
On Wed, Jan 11, 2012 at 2:13 PM, sunniejai sunnie...@gmail.com wrote:
Thanks Rob, a blog post would be great!
As I am not that
Hi there,
How do you sign the burn bootstrapper? Do you simply sign it with
signtool.exe after you build the executable? When I try it with the sign
tool, the UAC prompt still shows up with an unknown publisher.
Also, do you need to sign all of the MSI packages that will be downloaded
with the
Easiest way: override the MSBuild SignXxx targets defined in
wix2010.targets with your own targets.
I really need to get the blog post up about this. sigh/
On Tue, Jan 10, 2012 at 6:50 PM, Sunny Li sunnie...@gmail.com wrote:
Hi there,
How do you sign the burn bootstrapper? Do you simply sign
13 matches
Mail list logo
