SSL handshake failed: SSL error: A TLS warning alert has been received.

[Gero]

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)

I assume the old svn client version was 1.4.6:
http://packages.ubuntu.com/hardy/subversion The new version is 1.6.6.

The repository has other users for whom it continues to work.

Any ideas what is going on?

Thanks,
Gero.

[Lieven Govaerts]

Can you still access that folder with a web browser, without a
certificate warning?
I think 1.6.6 is more strict on validating server certificates as
1.4.6, not sure though.

Lieven

[Gero]

On Wed, 2010-08-11, Lieven Govaerts wrote:

Yes, web access still works with no warnings.

Gero.

[Lieven Govaerts]

Well, that error message isn't telling a lot. Might be interesting to
find out what's logged in the server's error log.

Lieven

[Nico Kadel-Garcia]

On Wed, Aug 11, 2010 at 10:24 AM, Gero <ge...@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?

>
> I assume the old svn client version was 1.4.6:
> http://packages.ubuntu.com/hardy/subversion The new version is 1.6.6.
>
> The repository has other users for whom it continues to work.
>
> Any ideas what is going on?
>

> Thanks,
> Gero.
>

[Larry Evans]

This is the 2nd thread that's mentioned ubuntu's lucid.
The last post to the other thread is found here:

http://article.gmane.org/gmane.comp.version-control.subversion.user/99801

Maybe ubuntu people have some idea what's wrong; however, I've
already posted a question here:

http://ubuntuforums.org/showthread.php?t=1561623

but have gotten no reply :(

[Larry Evans]

On 08/27/10 11:39, Larry Evans wrote:
[snip]

> This is the 2nd thread that's mentioned ubuntu's lucid.
> The last post to the other thread is found here:
>
> http://article.gmane.org/gmane.comp.version-control.subversion.user/99801
>
> Maybe ubuntu people have some idea what's wrong; however, I've
> already posted a question here:
>
> http://ubuntuforums.org/showthread.php?t=1561623
>
> but have gotten no reply :(

The solution to my problem is described here:

http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402527

[pweltz]

I also had this error "SSL handshake

failed: SSL error: A TLS warning alert has been received. "

In case it helps, here is how I found a solution:

-I did a trace: tcpdump port 443 -s0 -w error.cap
-which I opened with wireshark, and saw the server gave a TLS warning "TLSv1
Record Layer: Alert (Level: Warning, Description: Unrecognized Name)"
This one is even documented in wikipedia
http://en.wikipedia.org/wiki/Transport_Layer_Security
"TLS only; client's Server Name Indicator specified a hostname not supported
by the server"

I understood there was a mismatch between the ServerName in apache's
ssl.conf and the IP I used on the svn command line
I updated the ServerName and the error went away

Phil

--
View this message in context: http://old.nabble.com/SSL-handshake-failed%3A-SSL-error%3A-A-TLS-warning-alert-has-been-received.-tp29409554p33294811.html
Sent from the Subversion Users mailing list archive at Nabble.com.

[Stefan Sperling]

On Thu, Feb 09, 2012 at 09:07:19AM -0800, pweltz wrote:
>
> I also had this error "SSL handshake
> failed: SSL error: A TLS warning alert has been received. "
>
> In case it helps, here is how I found a solution:
>
> -I did a trace: tcpdump port 443 -s0 -w error.cap
> -which I opened with wireshark, and saw the server gave a TLS warning "TLSv1
> Record Layer: Alert (Level: Warning, Description: Unrecognized Name)"
> This one is even documented in wikipedia
> http://en.wikipedia.org/wiki/Transport_Layer_Security
> "TLS only; client's Server Name Indicator specified a hostname not supported
> by the server"
>
> I understood there was a mismatch between the ServerName in apache's
> ssl.conf and the IP I used on the svn command line
> I updated the ServerName and the error went away

Thanks for sharing this!

A similar (but more obscure) error message due to the same underlying
problem is documented in the FAQ:
http://subversion.apache.org/faq.html#ssl-error-336032856

I suppose we should add your error message to that FAQ entry, too.
Would you be able to provide a patch against
https://svn.apache.org/repos/asf/subversion/site/publish/faq.html
that makes this change?