> -----Original Message-----
> From: Gero [mailto:gero_at_ieee.org]
> Sent: maandag 6 september 2010 11:37
> To: users_at_subversion.apache.org
> Subject: Re: SSL handshake failed: SSL error: A TLS warning alert has been
> received.
>
> On Wed, 2010-08-18 at 02:06 -0400, Nico Kadel-Garcia wrote:
> On Wed, Aug 11, 2010 at 10:24 AM, Gero <gero_at_ieee.org> wrote:
> > > Hi,
> > >
> > > After moving to a new system (Kubuntu Hardy -> Lucid) I can no
> longer access
> > > an SVN repository:
> > >
> > > $ svn update
> > > svn: OPTIONS of 'https://example.com/path/to/svn/trunk': SSL
> handshake
> > > failed: SSL error: A TLS warning alert has been received.
> > > (https://example.com)
> >
> > But 'svn info 'https://example.com/path/to/svn/trunk works? What about
> > doing a clean checkout to a new location?
>
> 'svn info' with no arguments works and shows info about the repository
> in question. 'svn info <repo>', however, does not work, with the same
> error message as above. A clean checkout doesn't work either.
>
> There is an Ubuntu bug report about Subversion not playing with the
> latest libneon nor libneon-gnutls. Apparently, libneon now reports more
> SSL problems that Subversion should ignore, but doesn't.
Subversion uses neon and neon uses your SSL library. Subversion doesn't use
the ssl library directly.
So this should be fixed either in Neon or (to restore compatibility with the
older version) in the SSL library.
Bert
Received on 2010-09-06 11:41:53 CEST