-
Bug
-
Resolution: Incomplete
-
P3
-
None
-
8u121
-
x86_64
-
windows_7
FULL PRODUCT VERSION :
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
Problem still exists in that version
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]
A DESCRIPTION OF THE PROBLEM :
I can't any longer start a properly signed Webstart Application beginning from 8u121 (Bug is still in 8u131) because of a "Unsigned Ressource found in JAR" exception.
The application is singed using Java8u111.
It is exactly the behaviour described in this bug-report: https://bugs.openjdk.java.net/browse/JDK-8173632
But I don't understand why it is considered as no issue as the file mentined is created by the jarsigner.
Webstart applications signed using the current JDK 8u131 (or 8u121) mostly doesn't run on older Java versions but sporadically even not on the same JDK they signed with (multiple repeatation of the signing helps).
REGRESSION. Last worked in version 8u111
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Sign an application using 8u111 and run it using 8u121 or later.
The bug-report mentioned in the description provides a running application as test case.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Application should start.
ACTUAL -
Application fails due to a Unsigned Resource in JAR claim.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Don't use the mentioned verions (we still are on 8u111 as our Signingprocess is automated and we need to support many differen Java versions).
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
Problem still exists in that version
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]
A DESCRIPTION OF THE PROBLEM :
I can't any longer start a properly signed Webstart Application beginning from 8u121 (Bug is still in 8u131) because of a "Unsigned Ressource found in JAR" exception.
The application is singed using Java8u111.
It is exactly the behaviour described in this bug-report: https://bugs.openjdk.java.net/browse/JDK-8173632
But I don't understand why it is considered as no issue as the file mentined is created by the jarsigner.
Webstart applications signed using the current JDK 8u131 (or 8u121) mostly doesn't run on older Java versions but sporadically even not on the same JDK they signed with (multiple repeatation of the signing helps).
REGRESSION. Last worked in version 8u111
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Sign an application using 8u111 and run it using 8u121 or later.
The bug-report mentioned in the description provides a running application as test case.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Application should start.
ACTUAL -
Application fails due to a Unsigned Resource in JAR claim.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Don't use the mentioned verions (we still are on 8u111 as our Signingprocess is automated and we need to support many differen Java versions).
- relates to
-
JDK-8173632 Verification of Java Web Start Jar results in 'Unsigned resource' since Java 8 update 121
-
- Closed
-