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
- :
- Sigining does not work when proxy is provided in internet connection(LAN setting)
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
Jan 05, 2009
01:43 AM
Sigining does not work when proxy is provided in internet connection(LAN setting)
Hi,
We are creating a build for the patch which requires the signing the files (dll files) included as a components. It does not work, if we give the proxy in internet connection settings(LAN setting). It works fine if we use some other internet source like wireless internet connection.
Is there any specific reason for this or is it something related to connectivity problem?
We are creating a build for the patch which requires the signing the files (dll files) included as a components. It does not work, if we give the proxy in internet connection settings(LAN setting). It works fine if we use some other internet source like wireless internet connection.
Is there any specific reason for this or is it something related to connectivity problem?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 05, 2009
11:31 AM
Both signtool and signcode support timestamping your signature by contacting a trusted third party (Verisign by default). Perhaps those tools do not work properly with the proxy?
Timestamping is a good practice, as it ensures your signature remains valid until the timestamp server's certificate expires, which is generally much later than when your certificate expires. We've added a settings.xml option to override or remove the timestamp, but I think we did not add this until IS2009, and regardless I would not recommend removing it for any public releases.
Timestamping is a good practice, as it ensures your signature remains valid until the timestamp server's certificate expires, which is generally much later than when your certificate expires. We've added a settings.xml option to override or remove the timestamp, but I think we did not add this until IS2009, and regardless I would not recommend removing it for any public releases.