-
Bug
-
Resolution: Won't Fix
-
P4
-
None
-
1.1.6
-
generic
-
solaris_2.5.1
is not working.
This bug was fixed in 1.2 alpha2 under the bug number # 4044236.
Also there was one more related bug # 4058192 which caused the Signature
block to be in wrong format. This bug was also fixed in 1.2 alpha2.
The purpose of this bug is to back port those two fixes in to 1.1.6 or 1.1.7
so that IBM will be happy.
Here is the email from IBM:
The sun.security.pkcs.PKCS7 is comparing the signedData OBJECT IDENTIFIER
against ContentInfo.SIGNED_DATA_OID ::= 1.2.840.1113549.1.7.2 (set in
sun.security.pkcs.ContentInfo).
All the other Object identifiers set in ContentInfo have the same problem
(incorrect rsadsi).
Conform with "PKCS #7: Cryptographic Message Syntax Standard " (
ftp://ftp.rsa.com/pub/pkcs/ascii/pkcs-7.asc)
pkcs-7 OBJECT IDENTIFIER ::= { iso(1) member-body(2) US(840) rsadsi(113549
) pkcs(1) 7 }
data OBJECT IDENTIFIER ::= { pkcs-7 1 }
signedData OBJECT IDENTIFIER ::= { pkcs-7 2 }
envelopedData OBJECT IDENTIFIER ::= { pkcs-7 3 }
signedAndEnvelopedData OBJECT IDENTIFIER ::=
{ pkcs-7 4 }
digestedData OBJECT IDENTIFIER ::= { pkcs-7 5 }
encryptedData OBJECT IDENTIFIER ::= { pkcs-7 6 }
- relates to
-
JDK-4076437 SignerInfo.verify() uses only encryption algorithm, not digest algorithm
-
- Closed
-
-
JDK-4058192 Signature block file in signed JAR file has wrong format
-
- Closed
-
-
JDK-4070068 Digest-Algorithms: line in MANIFEST does not conform to spec.
-
- Closed
-
-
JDK-4082921 PKCS7.getCertificate() looks for subject name instead of issuer name
-
- Closed
-
-
JDK-4044236 PKCS #7 OIDS incorrect ... code signing not interoperable
-
- Closed
-
-
JDK-4061422 JarVerifierStream does not throw an exception on an invalid jar file
-
- Closed
-
-
JDK-4084799 jar signed on win32 is unverifiable by using JDK 1.1.4
-
- Closed
-
-
JDK-4094674 Applet digital signing fails with JDK 1.1.4 but OK with 1.1.3
-
- Closed
-