Hello Graham, I've made changes in SVNKit to make it support SNI "out of the box". The most recent version of SVNKit now sends correct request to the https://sni.velox.ch/ You may get new SVNKit binaries with these changes at http://teamcity.tmatesoft.com/viewLog.html?buildId=5276&tab=artifacts&buildTypeId=bt43
If possible, could you please try running checkout with that new version to see if it still hangs on connect? Thanks! Alexander Kitaev, TMate Software, http://subgit.com/ - Svn to Git Migration! http://svnkit.com/ - Java [Sub]Versioning Library! http://hg4j.com/ - Java Mercurial Library! http://sqljet.com/ - Java SQLite Library! On 5 February 2013 16:48, Alexander Kitaev <kit...@gmail.com> wrote: > Hello Graham, > >> It does work with other Java software, most specifically maven, which works >> out the box (on v3.0.3 or less, v3.0.4 has broken client certificate >> support, and requires a workaround). >> I understand the httpclient doesn't work properly with SNI, not sure if this >> affects svnkit: > > SVNKit uses plain SSLSocket, not HTTPClient, however in order to > support client certificates we implement our own KeyManager that may > not support SNI properly. > I've found a web site to test SNI on (https://sni.velox.ch/) and will > make sure that SVNKit does work with it. > > It is strange however, that Socket.connect(...) hangs, my expectation > would be an exception thrown... > Anyway, I'll make sure SVNKit does support SNI and then will send you > a build to test. > > Alexander Kitaev, > TMate Software, > http://subgit.com/ - Svn to Git Migration! > http://svnkit.com/ - Java [Sub]Versioning Library! > http://hg4j.com/ - Java Mercurial Library! > http://sqljet.com/ - Java SQLite Library! > > > On 4 February 2013 23:42, Graham Leggett <minf...@sharp.fm> wrote: >> On 05 Feb 2013, at 12:25 AM, Alexander Kitaev <kit...@gmail.com> wrote: >> >>>> The native subversion client performs SNI correctly out of the box, as >>>> does Java 7. Svnkit doesn't set the name of the host as required, and so >>>> doesn't work. >>> >>> Could you please provide more information on that? >>> Do you run "jsvn" with Java 7 and necessary -D system property and SNI >>> is still not working? Does it work with other Java software? >> >> It does work with other Java software, most specifically maven, which works >> out the box (on v3.0.3 or less, v3.0.4 has broken client certificate >> support, and requires a workaround). >> >> I understand the httpclient doesn't work properly with SNI, not sure if this >> affects svnkit: >> >> http://stackoverflow.com/questions/12361090/server-name-indication-sni-on-java >> >> Regards, >> Graham >> -- >>
