asked on 7/24/2008

Visual studio setup project - digitally sign msi (publisher cannot be verified error)

I created a MSI file and a couple of EXE's. Need to sign them and upload them to the production server so that users can download them and run on their local machines.

I have the certificate file and using the following command, i signed:
signtool.exe sign /f certicate_Test.pfx /t "http://timestamp.verisign.com/scripts/timestamp.dll" /v msiFileName

The above command was executed successfully. I uploaded it to the production server and when i downloaded to another PC and tried running it, gave me an error "Publisher cannot be verified". Is there something i need to do on the remote PC's where the msi is going to be executed?

OS Security Installation .NET Programming

Last Comment

Vadim Rapp

7/24/2008

ASKER CERTIFIED SOLUTION

Vadim Rapp

7/24/2008

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

vizagboy

7/24/2008

ASKER

Say, for eg., this is the certificate key we purchased certicate_Test.pfx. So firstly, i need to find out the certification authority right. What else is required to be performed on the end user's machine setup wise? They are not on the same domain.

Vadim Rapp

7/24/2008

User's machine needs to trust certification authority that has issued your certificate. Certification and trust is a whole big area, you will need to become familiar with it to some degree. For starters, run mmc.exe, add snap-in "certificates", and explore what you see, specifically, certification authorities.