Details
-
Type:
Enhancement
-
Status: Closed
-
Priority:
P5
-
Resolution: Fixed
-
Affects Version/s: 7
-
Fix Version/s: 7
-
Component/s: security-libs
-
Labels:
-
Subcomponent:
-
Resolved In Build:b138
-
CPU:generic
-
OS:generic
-
Verification:Verified
Description
When a TSA is not accessible, jarsigner would print out:
jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall then an HTTP proxy may need to be specified. Supply the following options to jarsigner:
-J-Dhttp.proxyHost=<hostname>
-J-Dhttp.proxyPort=<portnumber>
In fact, most TSAs are behind SSL, and I've already seen several customers complaining the system properties do not work. In this case, they should be https.proxyHost and https.proxyPort.
jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall then an HTTP proxy may need to be specified. Supply the following options to jarsigner:
-J-Dhttp.proxyHost=<hostname>
-J-Dhttp.proxyPort=<portnumber>
In fact, most TSAs are behind SSL, and I've already seen several customers complaining the system properties do not work. In this case, they should be https.proxyHost and https.proxyPort.
Activity
BT2:EVALUATION
Changed to:
jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall an HTTP or HTTPS proxy may need to be specified. Supply the following options to jarsigner:
-J-Dhttp.proxyHost=<hostname>
-J-Dhttp.proxyPort=<portnumber>
or
-J-Dhttps.proxyHost=<hostname>
-J-Dhttps.proxyPort=<portnumber>
Changed to:
jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall an HTTP or HTTPS proxy may need to be specified. Supply the following options to jarsigner:
-J-Dhttp.proxyHost=<hostname>
-J-Dhttp.proxyPort=<portnumber>
or
-J-Dhttps.proxyHost=<hostname>
-J-Dhttps.proxyPort=<portnumber>
http://hg.openjdk.java.net/jdk7/tl/jdk/rev/c43811a602a8