Feature Requests item #1812933, was opened at 2007-10-13 17:00
Message generated for change (Comment added) made by barnson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1812933&group_id=105970
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: linker
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Chris Ridd (chrisridd)
Assigned to: Nobody/Anonymous (nobody)
Summary: Produce digitally signed packages
Initial Comment:
Currently it appears that to produce digitally signed MSI packages one must use
the Microsoft signtool.exe program.
It would be nice if light.exe (or whatever's appropriate) could be enhanced to
also do this.
----------------------------------------------------------------------
>Comment By: Bob Arnson (barnson)
Date: 2007-10-29 01:18
Message:
Logged In: YES
user_id=26581
Originator: NO
What's the benefit of embedding signing, other than saving one step in a
build process?
----------------------------------------------------------------------
Comment By: Chris Ridd (chrisridd)
Date: 2007-10-17 08:16
Message:
Logged In: YES
user_id=47646
Originator: YES
That's great, but only if you're using "MSBuild" to do your building. If
you're not... :-(
----------------------------------------------------------------------
Comment By: r_k (rkuki)
Date: 2007-10-15 19:45
Message:
Logged In: YES
user_id=1913821
Originator: NO
You can customize the MSBuild target "AfterBuild" in the wixproj file.
This is an example, which generates setup.exe and signs the MSI and
setup.exe:
<PropertyGroup>
<Certificate>FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF</Certificate>
<TimeStampUrl>http://timestamp.verisign.com/scripts/timstamp.dll</TimeStampUrl>
<ProductName>My Product</ProductName>
</PropertyGroup>
<ItemGroup>
<BootstrapperFile Include="Microsoft.Windows.Installer.2.0">
<ProductName>Windows Installer 2.0</ProductName>
</BootstrapperFile>
</ItemGroup>
<ItemGroup>
<InstallerToSign Include="$(OutputPath)$(OutputName).msi" />
<SetupToSign Include="$(OutputPath)Setup.exe" />
<InstallerMsi Include="$(OutputName).msi" />
</ItemGroup>
<Target Name="AfterBuild">
<Exec Command="signtool sign /sha1 $(Certificate)
"@(InstallerToSign)"" />
<GenerateBootstrapper ApplicationFile="@(InstallerMsi)"
ApplicationName="$(ProductName)" BootstrapperItems="@(BootstrapperFile)"
ComponentsLocation="Relative" Culture="de" FallbackCulture="de-DE"
CopyComponents="True" Validate="False" OutputPath="$(OutputPath)" />
<SignFile CertificateThumbprint="$(Certificate)"
SigningTarget="@(SetupToSign)" TimestampUrl="$(TimeStampUrl)" />
</Target>
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1812933&group_id=105970
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
