-
Bug
-
Resolution: Fixed
-
P1
-
8
-
b127
-
linux
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8032748 | 9 | Weijun Wang | P1 | Closed | Fixed | b03 |
JDK-8033351 | 8u20 | Weijun Wang | P1 | Closed | Fixed | b01 |
JDK-8033641 | 8u11 | Weijun Wang | P1 | Resolved | Fixed | b01 |
JDK-8033318 | 8u5 | Weijun Wang | P1 | Resolved | Fixed | b07 |
JDK-8035229 | emb-8u6 | Weijun Wang | P1 | Closed | Fixed | b06 |
JDK-8033246 | 7u80 | Weijun Wang | P1 | Resolved | Fixed | b01 |
JDK-8060943 | 7u79 | Weijun Wang | P1 | Resolved | Fixed | b01 |
JDK-8057414 | 7u76 | Weijun Wang | P1 | Resolved | Fixed | b01 |
JDK-8034716 | 7u65 | Weijun Wang | P1 | Resolved | Fixed | b01 |
JDK-8032442 | 7u60 | Weijun Wang | P1 | Closed | Fixed | b05 |
java version "1.8.0-ea"
Java(TM) SE Runtime Environment (build 1.8.0-ea-b121)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b63, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux tc 3.12.6-1-ARCH #1 SMP PREEMPT Fri Dec 20 19:39:00 CET 2013 x86_64 GNU/Linux
A DESCRIPTION OF THE PROBLEM :
In Apache maven-jarsigner-plugin we got a regression around the jarsigner -verify command applyed to a unsigned jar.
With jdk 1.7.0_45:
$> jarsigner -verify tampered.jar
jarsigner: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
Exit code is 1.
With jdk 1.8.0:
$> jarsigner -verify tampered.jar
jar is unsigned. (signatures missing or not parsable)
Exit code is 0.
REGRESSION. Last worked in version 7u45
ADDITIONAL REGRESSION INFORMATION:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Try on a bad signed jar:
svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jarsigner-plugin/src/it/verify-fail/tampered.jar
run on it jarsigner -verify tampered.jar
or
Get the maven-jarsigner-plugin and execute the verify-fail IT
svn co http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jarsigner-plugin
cd maven-jarsigner-plugin
mvn verify -Prun-its -Dinvoker.pom=src/it/verify-fail/pom.xml
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Exit code = 1
ACTUAL -
Exit code = 0
REPRODUCIBILITY :
This bug can be reproduced always.
- backported by
-
JDK-8033246 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8033318 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8033641 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8034716 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8057414 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8060943 jarsigner -verify exits with 0 when a jar file is not properly signed
- Resolved
-
JDK-8032442 jarsigner -verify exits with 0 when a jar file is not properly signed
- Closed
-
JDK-8032748 jarsigner -verify exits with 0 when a jar file is not properly signed
- Closed
-
JDK-8033351 jarsigner -verify exits with 0 when a jar file is not properly signed
- Closed
-
JDK-8035229 jarsigner -verify exits with 0 when a jar file is not properly signed
- Closed
- relates to
-
JDK-8237604 [TEST_BUG] sun/security/tools/jarsigner/EntriesOrder.java not adapted for changes in JDK-7194449
- Resolved
-
JDK-8021788 JarInputStream doesn't provide certificates for some file under META-INF
- Closed
-
JDK-8031748 Clarify jar entry orders in a jar file
- Closed