You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by fx...@ws.apache.org on 2004/07/19 14:46:39 UTC
[jira] Created: (WSFX-22) Merlin crypto hardcodes the use of BC for certificate path validation
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-22
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-22
Summary: Merlin crypto hardcodes the use of BC for certificate path validation
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Christof Soehngen
Created: Mon, 19 Jul 2004 5:45 AM
Updated: Mon, 19 Jul 2004 5:45 AM
Environment: CVS snapshot from 2004-07-19
Description:
As Jason Essington stated via the mailing-list:
> Merlin.java claims to be a java 1.4 crypto implementation,
> however the validateCertPath method requires api's from
> the java 1.3 version of BouncyCastle.
> Since Merlin is a Java1.4 implementation shouldn't we change
> all the cert path stuff from the org.bouncycastle.jce.cert
> package to the Java 1.4 package java.security.cert?
> This would allow wss4j (and merlin specifically) to function
> with Java 1.4 and the BouncyCastle java 1.4 provider.
Some versions ago, certs read with BC could not be validated with the sun CertPathValidator. Using the sun factory to explicitly load the BC validator (CertPathValidator.getInstance("PKIX", "BC");) is not possible, too (I'm not 100% sure, but I think BC does not inherit from the sun class, wich is checked by the factory). So the only possiblity was using the hardcoded version.
With BC 1.23, this is not necessary anymore. I suggest using the attached patch.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (WSFX-22) Merlin crypto hardcodes the use of BC for certificate path validation
Posted by fx...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Mon, 19 Jul 2004 6:43 AM
Thanks Christof. Applied your patch.
-- dims
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-22
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-22
Summary: Merlin crypto hardcodes the use of BC for certificate path validation
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Christof Soehngen
Created: Mon, 19 Jul 2004 5:45 AM
Updated: Mon, 19 Jul 2004 6:43 AM
Environment: CVS snapshot from 2004-07-19
Description:
As Jason Essington stated via the mailing-list:
> Merlin.java claims to be a java 1.4 crypto implementation,
> however the validateCertPath method requires api's from
> the java 1.3 version of BouncyCastle.
> Since Merlin is a Java1.4 implementation shouldn't we change
> all the cert path stuff from the org.bouncycastle.jce.cert
> package to the Java 1.4 package java.security.cert?
> This would allow wss4j (and merlin specifically) to function
> with Java 1.4 and the BouncyCastle java 1.4 provider.
Some versions ago, certs read with BC could not be validated with the sun CertPathValidator. Using the sun factory to explicitly load the BC validator (CertPathValidator.getInstance("PKIX", "BC");) is not possible, too (I'm not 100% sure, but I think BC does not inherit from the sun class, wich is checked by the factory). So the only possiblity was using the hardcoded version.
With BC 1.23, this is not necessary anymore. I suggest using the attached patch.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (WSFX-22) Merlin crypto hardcodes the use of BC for certificate path validation
Posted by fx...@ws.apache.org.
The following issue has been updated:
Updater: Christof Soehngen (mailto:christof.soehngen@syracom.de)
Date: Mon, 19 Jul 2004 5:46 AM
Changes:
Attachment changed to Merlin.java.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/WSFX-22?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/WSFX-22
Here is an overview of the issue:
---------------------------------------------------------------------
Key: WSFX-22
Summary: Merlin crypto hardcodes the use of BC for certificate path validation
Type: Bug
Status: Unassigned
Priority: Major
Project: WSFX
Components:
WSS4J
Assignee:
Reporter: Christof Soehngen
Created: Mon, 19 Jul 2004 5:45 AM
Updated: Mon, 19 Jul 2004 5:46 AM
Environment: CVS snapshot from 2004-07-19
Description:
As Jason Essington stated via the mailing-list:
> Merlin.java claims to be a java 1.4 crypto implementation,
> however the validateCertPath method requires api's from
> the java 1.3 version of BouncyCastle.
> Since Merlin is a Java1.4 implementation shouldn't we change
> all the cert path stuff from the org.bouncycastle.jce.cert
> package to the Java 1.4 package java.security.cert?
> This would allow wss4j (and merlin specifically) to function
> with Java 1.4 and the BouncyCastle java 1.4 provider.
Some versions ago, certs read with BC could not be validated with the sun CertPathValidator. Using the sun factory to explicitly load the BC validator (CertPathValidator.getInstance("PKIX", "BC");) is not possible, too (I'm not 100% sure, but I think BC does not inherit from the sun class, wich is checked by the factory). So the only possiblity was using the hardcoded version.
With BC 1.23, this is not necessary anymore. I suggest using the attached patch.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira