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

Re: SSL handshake failed: SSL alert received

From: Brandon L. Wisenburg <brandon_at_wisenburg.com>
Date: Thu, 12 Jul 2018 13:34:32 +0000

Hi Philip
Thanks for the reply. The odd part is when I do the openssl s_client it looks like the handshake is successful.

----- Original Message -----
From: "Philip Martin" <philip_at_codematters.co.uk>
To: "Philip Martin" <philip_at_codematters.co.uk>
Cc: "brandon" <brandon_at_wisenburg.com>, "users" <users_at_subversion.apache.org>
Sent: Thursday, July 12, 2018 4:38:46 AM
Subject: Re: SSL handshake failed: SSL alert received

Philip Martin <philip_at_codematters.co.uk> writes:

> "Brandon L. Wisenburg" <brandon_at_wisenburg.com> writes:
>
>> svn update
>> svn: OPTIONS of 'https://domain/src': SSL handshake failed: SSL alert
>> received: Handshake failed (https://www.domain.com)
>
> You don't say which version of Subversion you are using but that looks
> like an old client as a newer client would include an error number in
> the error message. An old client probably uses an old SSL library and
> it is possible that the client's SSL library doesn't support the SSL
> connection that the server is trying to establish.
>
> If the client has the OpenSSL tools installed you can use
>
> openssl s_client -connect domain:443
>
> to see lots of detail about the SSL negotiation.

That may not be the problem. The client appears to have sent an OPTIONS
request which happens after the SSL connection has been established.

If the client has the socat proxy installed you can use the instructions
here:

https://subversion.apache.org/docs/community-guide/debugging.html#net-trace-socat

to get a network trace of the OPTIONS request and response.

-- 
Philip
Received on 2018-07-12 15:42:02 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.