[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Update to svn version 1.5.x leads to "SSL negotiation failed: Secure connection truncated"

From: Niklaus Giger <niklaus.giger_at_member.fsf.org>
Date: Mon, 1 Dec 2008 20:36:39 +0100


Subversion is a great tool which I use a lot at work and at home. The
developers did a great job!

However when I upgrade my Debian package from 1.4.2 to 1.5.4 my access to our
server suddenly broke with the error messag "SSL negotiation failed: Secure
connection truncated".

The Debian package maintainer suggested (as shown in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507374)suggested the followin
workaround which worked perfectyl for me:
> Subversion 1.5 ships with two http/https backend libraries that use two
> different WebDAV libraries, neon and serf. Try the following in
> ~/.subversion/servers:
> [groups]
> foobar = svnte.netstal.com
> [foobar]
> http-library = serf
> (Of course "foobar" can be any label.) The serf backend prompts me for
> a client certificate. This may or may not be what you need, but at
> least it is different from what the neon backend does.

I did not find any reference to this solution. Therefore I repost here if
anybody has the same problem.

This problem only affects repositories where I need to specify a CERT file in
my ~/.subversion/servers file, where you find lines like
> ssl-client-cert-file = /path/to/myCrediental.pfx
> ssl-client-cert-password = topsecret

I do not whether one should add this to the FAQ (or whether it is a very
uncommon errror).

Best regards


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-12-01 20:58:41 CET

This is an archived mail posted to the Subversion Users mailing list.