I've been signing and deploying for several years now, but with the latest
release I've ran into a strange problem. The first error complains about a
difference in size between the certificate in the CAB verses what's in the
package. The second error is a bit comical complaining that the digital
signature is invalid, but WinVerifyTrust returned 0. If I peek into the
Package Cache, looking at the CAB and the MSI, both show as having a valid
digital signature. Using Orca and extracting the certificate embedded in the
MSI shows the same certificate which is valid.
Log Below:
MSI (s) (B0:2C) [15:41:26:011]: Validating digital signature of file
'C:\ProgramData\Package
Cache\{6A07C6E2-08CD-4F38-BF9D-38332A4DA077}v4.13.1.0\payload\AFC.cab'
MSI (s) (B0:2C) [15:41:27:007]: Certificate of signed file
'C:\ProgramData\Package
Cache\{6A07C6E2-08CD-4F38-BF9D-38332A4DA077}v4.13.1.0\payload\AFC.cab' differs
in size with the certificate authored in the package
MSI (s) (B0:34) [15:41:27:007]: Note: 1: 1330 2: C:\ProgramData\Package
Cache\{6A07C6E2-08CD-4F38-BF9D-38332A4DA077}v4.13.1.0\payload\AFC.cab 3: 0
MSI (s) (B0:34) [15:41:27:007]: Note: 1: 2205 2: 3: Error
MSI (s) (B0:34) [15:41:27:007]: Note: 1: 2228 2: 3: Error 4: SELECT `Message`
FROM `Error` WHERE `Error` = 1330
MSI (s) (B0:34) [16:59:59:459]: Note: 1: 2205 2: 3: Error
MSI (s) (B0:34) [16:59:59:459]: Note: 1: 2228 2: 3: Error 4: SELECT `Message`
FROM `Error` WHERE `Error` = 1709
MSI (s) (B0:34) [16:59:59:459]: Product: FOO -- Error 1330. A file that is
required cannot be installed because the cabinet file C:\ProgramData\Package
Cache\{6A07C6E2-08CD-4F38-BF9D-38332A4DA077}v4.13.1.0\payload\AFC.cab has an
invalid digital signature. This may indicate that the cabinet file is corrupt.
Error 0 was returned by WinVerifyTrust.
Note, on the build machine I have the certificate in the store so the selection
is automatic.
<Target Name="SignCabs" DependsOnTargets="UsesSignTool">
<Exec Command=""$(SignToolPath)" sign /t
http://timestamp.digicert.com /a "%(SignCabs.FullPath)"" />
</Target>
<Target Name="SignMsi" DependsOnTargets="UsesSignTool">
<Exec Command=""$(SignToolPath)" sign /d "FOO Setup" /t
http://timestamp.digicert.com /a "%(SignMsi.FullPath)"" />
</Target>
Thanks,
Jacob
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
