This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: private key password popup
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
12:29 PM
private key password popup
I am using basic MSI project.
The private key for signature is specified in the release configuration.
However, sometimes there is still a "enter private key" dialog popup at the end of the build.
Since we are using command line to build our projects, this is quite annoying as it waits human input. The strange thing is that it happens sometimes, not always.
Please advise. Thanks!
The private key for signature is specified in the release configuration.
However, sometimes there is still a "enter private key" dialog popup at the end of the build.
Since we are using command line to build our projects, this is quite annoying as it waits human input. The strange thing is that it happens sometimes, not always.
Please advise. Thanks!
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 09, 2008
12:48 PM
If you use a .pfx file as your signature file you should no longer get these prompts. When you use a .pfx (personal information exchange) file, InstallShield will use signtool.exe to sign your files, which will accept a command-line parameter to pass in the password. This note from our help explains this:
Using a .pfx file is often the preferred method for digitally signing files, since it is more likely to work in many different environments (such as locked build machines). Since the SignTool.exe utility accepts the password as a command-line parameter, it can be automatically provided even in scenarios where Signcode.exe cannot accept the password. Therefore, if you specify the digital signature password in InstallShield, you will never see a password prompt if you are using a .pfx file.
Using a .pfx file is often the preferred method for digitally signing files, since it is more likely to work in many different environments (such as locked build machines). Since the SignTool.exe utility accepts the password as a command-line parameter, it can be automatically provided even in scenarios where Signcode.exe cannot accept the password. Therefore, if you specify the digital signature password in InstallShield, you will never see a password prompt if you are using a .pfx file.
(If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
08:44 AM
Thanks. Where can I obtain .pfx files?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 10, 2008
12:23 PM
You can use Microsoft tools PVK2PFX.exe and pvkimprt.exe to create the .pfx file from your .spc and .pvk files.
See the following help topic to get you started:
http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=isxhelp14-DigitalSigningSecurityhtm&sliceId=&docTypeID=DT_MACROVISIONHELPNET_1_1&dialogID=9400726&stateId=0%200%209402311
See the following help topic to get you started:
http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=isxhelp14-DigitalSigningSecurityhtm&sliceId=&docTypeID=DT_MACROVISIONHELPNET_1_1&dialogID=9400726&stateId=0%200%209402311
(If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)