Re: [WiX-users] Using signtool to sign bootstrapper

Yes I understand the difference between /t and /tr. They are two different methods of getting the time stamp which means that comodoca (and each of the other time stamp vendors) actually have two timestamp servers (authenticode and rfc3161). I was just pointing out that for me when I tested it a

Re: [WiX-users] Using signtool to sign bootstrapper

This was an issue but I resolved it by using: /tr http://timestamp.comodoca.com/rfc3161 /tr Specifies the URL of the RFC 3161 time stamp server and is somehow different than /t (I didn't dig into the differences) It appears the problem I was encountering was due to the Crystal Report MSM (see my

Re: [WiX-users] Using signtool to sign bootstrapper

I just noticed that: http://timestamp.comodoca.com/rfc3161 is returning: 000.
0%#Bad request format or system error. I do not know if this is related to your issue. Using /t "http://timestamp.comodoca.com/authenticode"; seems to work for me. -- View this message in context: http://wi

Re: [WiX-users] Using signtool to sign bootstrapper

What does the output of MSBuild look like when you build your bundle? Is signtool being called? (If you can't see it in the logs, you may have to increase the verbosity.) For the MSI/CABS, http://timestamp.digicert.com /a "%(SignCabs.FullPath)"" /> http://timestamp.digicert