[ 
https://jira.codehaus.org/browse/WAGON-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318092#comment-318092
 ] 

Graham Leggett commented on WAGON-372:
--------------------------------------

Sorry, should have been more specific, this was with 
-Dmaven.wagon.http.ssl.easy=false. If we switch 
-Dmaven.wagon.http.ssl.easy=true, we also get the keystore being ignored, but 
in this case we fail with a handshake failure instead of peer is not 
authenticated.

In both cases (false or true), Server Name Indication (RFC3546) breaks, the SSL 
handshake debug log shows the wrong certificate being sent by the server (the 
first certificate). Once the http-lightweight wagon v2.2 workaround is put in 
place, SNI starts working again and the server sends the correct certificate. I 
suspect whatever SSL options that the new code is setting, it is 
unintentionally switching other SSL options like SNI off.

                
> SSL client-side certificates stopped working in maven 3.0.4
> -----------------------------------------------------------
>
>                 Key: WAGON-372
>                 URL: https://jira.codehaus.org/browse/WAGON-372
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 2.2
>         Environment: Fedora, Ubuntu
>            Reporter: Igor von Nyssen
>
> The following command works perfectly in Maven 3.0.3, but 3.0.4 does not seem 
> to open the key store and therefore client side certificate authentication 
> fails as maven never presents a certificate to the server.
> mvn deploy -Djavax.net.ssl.keyStore=/home/<user>/ssl/key.p12 
> -Djavax.net.ssl.keyStorePassword=****** -Djavax.net.ssl.keyStoreType=pkcs12
> adding -Djavax.net.debug=all reveals that the keystore is never loaded. 
> Confirmed with strace that the keystore file is never touched or opened.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to