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 e
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
Reco
The same problem has just manifested when using ubuntu lucid either due to a
package update or possibly changes on the server side. I now get the
following error when attempting an svn update (svn info works fine).
SSL handshake failed: SSL error: A TLS warning alert has been received.
I
On Mon, Sep 6, 2010 at 5:40 AM, Bert Huijben wrote:
>
>
>> -Original Message-
>> From: Gero [mailto:g...@ieee.org]
>> Sent: maandag 6 september 2010 11:37
>> To: users@subversion.apache.org
>> Subject: Re: SSL handshake failed: SSL error: A TLS warning
> -Original Message-
> From: Gero [mailto:g...@ieee.org]
> Sent: maandag 6 september 2010 11:37
> To: users@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
Forgot the link to the Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/294648
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 ch
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'v
id) 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.
>
On Wed, Aug 11, 2010 at 10:24 AM, Gero 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: SS
ry:
>> >
>> > $ 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 cl
e.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.
> >
On Wed, Aug 11, 2010 at 4:24 PM, Gero 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: SS
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 assum
14 matches
Mail list logo
