You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexander Kleymenov (JIRA)" <ji...@apache.org> on 2006/11/01 10:21:52 UTC
[jira] Created: (HARMONY-2029) [classlib][x-net] JSSE Provider
fails while communicating with 3rd party TLS server
[classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
-----------------------------------------------------------------------------------
Key: HARMONY-2029
URL: http://issues.apache.org/jira/browse/HARMONY-2029
Project: Harmony
Issue Type: Bug
Components: Classlib
Reporter: Alexander Kleymenov
JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-2029) [classlib][x-net] JSSE Provider
fails while communicating with 3rd party TLS server
Posted by "Alexander Kleymenov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2029?page=comments#action_12449984 ]
Alexander Kleymenov commented on HARMONY-2029:
----------------------------------------------
Looks fine. Thank you!
> [classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2029
> URL: http://issues.apache.org/jira/browse/HARMONY-2029
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexander Kleymenov
> Assigned To: Stepan Mishura
> Attachments: patch-ds.txt
>
>
> JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
> The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
> K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (HARMONY-2029) [classlib][x-net] JSSE Provider
fails while communicating with 3rd party TLS server
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2029?page=all ]
Stepan Mishura resolved HARMONY-2029.
-------------------------------------
Resolution: Fixed
Thanks Alexander, the patch was applied to X-NET module at r475198.
Please check that the patch was applied as you expected.
> [classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2029
> URL: http://issues.apache.org/jira/browse/HARMONY-2029
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexander Kleymenov
> Assigned To: Stepan Mishura
> Attachments: patch-ds.txt
>
>
> JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
> The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
> K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2029) [classlib][x-net] JSSE Provider
fails while communicating with 3rd party TLS server
Posted by "Alexander Kleymenov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2029?page=all ]
Alexander Kleymenov updated HARMONY-2029:
-----------------------------------------
Attachment: patch-ds.txt
Currently the certificate_verify message for client's certificate with RSA keys is signed with the cipher obtained by Cipher.getInstance("RSA"). Bouncy Castle Crypto provider (used with Harmony) for "RSA" transformation returns cipher corresponding to "RSA/ECB/NoPadding" transformation while TLS specification demands using of "RSA/ECB/PKCS1Padding". (BTW: JCE for "RSA" returns cipher corresponding to "RSA/ECB/PKCS1Padding"). So the problem is in ambiguous transformation string used for cipher creation. It should be more detailed.
Attached patch fixes this problem.
> [classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2029
> URL: http://issues.apache.org/jira/browse/HARMONY-2029
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexander Kleymenov
> Attachments: patch-ds.txt
>
>
> JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
> The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
> K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (HARMONY-2029) [classlib][x-net] JSSE Provider fails
while communicating with 3rd party TLS server
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2029?page=all ]
Stepan Mishura closed HARMONY-2029.
-----------------------------------
Verified by Alexander.
> [classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2029
> URL: http://issues.apache.org/jira/browse/HARMONY-2029
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexander Kleymenov
> Assigned To: Stepan Mishura
> Attachments: patch-ds.txt
>
>
> JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
> The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
> K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (HARMONY-2029) [classlib][x-net] JSSE Provider
fails while communicating with 3rd party TLS server
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2029?page=all ]
Stepan Mishura reassigned HARMONY-2029:
---------------------------------------
Assignee: Stepan Mishura
> [classlib][x-net] JSSE Provider fails while communicating with 3rd party TLS server
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2029
> URL: http://issues.apache.org/jira/browse/HARMONY-2029
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexander Kleymenov
> Assigned To: Stepan Mishura
> Attachments: patch-ds.txt
>
>
> JSSE Provider fails while communicating with 3rd party TLS server demanding mutual authentication.
> The failure is reproducible if the client's certificate contains RSA key. Stack trace for failure is:
> K0319javax.net.ssl.SSLException: Fatal alert received bad_certificate
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.processAlert(SSLSocketImpl.java:791)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.doHandshake(SSLSocketImpl.java:732)
> at org.apache.harmony.xnet.provider.jsse.SSLSocketImpl.startHandshake(SSLSocketImpl.java:438)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira