Hi all,

I am currently trying to get Jenkins to talk to an svn repository secured by 
client certificates, and am not getting anything more useful out of the process 
than the following:

Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection 
during handshake
        at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:946)
        at 
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1328)
        at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:702)
        at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:122)
        at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.sendData(HTTPConnection.java:313)

First off, does svnkit support client certificates, and if so, how do you 
configure them? I have not found any clear documentation for this. Am I right 
in guessing that svnkit uses the same configuration files as the native 
subversion command line client (which works fine)?

Secondly, does svnkit do anything special to the connection handling that would 
stop Java's ordinary SSL handling from working using -D options? Passing the 
same -D options that work with maven to the java process running svnkit doesn't 
seem to make a difference.

Lastly, does svnkit do anything that would break Java7's native support for SNI?

Regards,
Graham
--

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to