;https://svn.corp.agrant.cn:25941/svn/com.agrantsem.datacollector':
> Could not read status line: SSL error: GnuTLS internal error.
> (https://svn.corp.agrant.cn:25941)
>
> Anyone has any insight on this?
Try using the correct passphrase for decrypting your client ce
rsion/auth/lei.w.p12':
Passphrase for '/home/lei.wang/.subversion/auth/lei.w.p12':
Passphrase for '/home/lei.wang/.subversion/auth/lei.w.p12':
svn: OPTIONS of
'https://svn.corp.agrant.cn:25941/svn/com.agrantsem.datacollector': Could not
read status li
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
Hi,
I've got the error message in the subject a few times, but after 1 or 2
retries, the update command succeeds.
The interesting part is that the command is executed on the server,
where the svn is located.
Does anybody know, how to fix this?
Thank you for your help,
Best regards,
Peter Bal
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
, Steve
Cc: users@subversion.apache.org
Subject: Re: Windows SSL Error
2011/4/26 Platz, Steve :
> Our Entrust SSL certificate recently expired and was replaced with a
> new one utilizing a certificate chain. Since installing the new
> certificate, access to a front-end website using
2011/4/26 Platz, Steve :
> Our Entrust SSL certificate recently expired and was replaced with a new one
> utilizing a certificate chain. Since installing the new certificate, access
> to a front-end website using this same certificate has been unaffected.
> However, we’re now seeing issues when we
4:15 PM
> To: Platz, Steve
> Cc: users@subversion.apache.org
> Subject: Re: Windows SSL Error
>
> And what about the system-wide file then? /etc/subversion/servers?
>
> On Tue, Apr 26, 2011 at 9:53 PM, Platz, Steve wrote:
>> For those Linux servers that I've trie
Same thing there as well.
-Original Message-
From: Johan Corveleyn [mailto:jcor...@gmail.com]
Sent: Tuesday, April 26, 2011 4:15 PM
To: Platz, Steve
Cc: users@subversion.apache.org
Subject: Re: Windows SSL Error
And what about the system-wide file then? /etc/subversion/servers?
On Tue
entries under [global] or [groups].
>
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: Tuesday, April 26, 2011 3:49 PM
> To: Platz, Steve
> Cc: users@subversion.apache.org
> Subject: Re: Windows SSL Error
>
> On Tue, Apr 26, 201
il 26, 2011 3:49 PM
To: Platz, Steve
Cc: users@subversion.apache.org
Subject: Re: Windows SSL Error
On Tue, Apr 26, 2011 at 6:06 PM, Platz, Steve wrote:
> Our Entrust SSL certificate recently expired and was replaced with a
> new one utilizing a certificate chain. Since installing the new
&g
On Tue, Apr 26, 2011 at 6:06 PM, Platz, Steve wrote:
> Our Entrust SSL certificate recently expired and was replaced with a new one
> utilizing a certificate chain. Since installing the new certificate, access
> to a front-end website using this same certificate has been unaffected.
> However, we
Our Entrust SSL certificate recently expired and was replaced with a new one
utilizing a certificate chain. Since installing the new certificate, access to
a front-end website using this same certificate has been unaffected. However,
we're now seeing issues when we attempt to check out/update/b
On Fri, 2010-12-17 at 11:03 -0500, r...@elilabs.com wrote:
> Thanks for this problem description and resolution. I was using an
> older
> version of TSVN and was asked (told) to upgrade to the latest. Now I
> can't even log into the server. From the description below, I think I
> have the same p
ows machine
>> > for a long time (many months), I cannot give a more accurate
>> timeframe.
>> >
>> > The error I get when I try to checkout via the svn.exe CLI is (I
>> masked
>> > my domain & path):
>> >
>> > c:\ svn.exe chec
't used svn on my windows machine
> > for a long time (many months), I cannot give a more accurate timeframe.
> >
> > The error I get when I try to checkout via the svn.exe CLI is (I masked
> > my domain & path):
> >
> > c:\ svn.exe checkout https://.c
ne
> for a long time (many months), I cannot give a more accurate timeframe.
>
> The error I get when I try to checkout via the svn.exe CLI is (I masked
> my domain & path):
>
> c:\ svn.exe checkout https://.com/
> svn: OPTIONS of 'https://.com/':
> SSL negotia
error I get when I try to checkout via the svn.exe CLI is (I masked
my domain & path):
c:\ svn.exe checkout https://.com/
svn: OPTIONS of 'https://.com/':
SSL negotiation failed: SSL error code -1/1/336032856
(https://.com)
My svn server is running via Apache. Client and server
> So I guess the problem is this specific client certificate
> though I still do not know what specifically.
>
Try using that cert on one of the machines with the 0.9.8g openSSL to
verify if it is that cert. You'll have to make sure you have both the
private and public key to do the authentica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey,
>> The access via the dav_svn module in a web browser from the
>> failing client works like a charm. There are no error
>> messages, the SSL handshake works fine. the content of the
>> repository is shown in the browser. This also works from
>
> One Thing of note that I forgot in my initial post and that
> was partially mentioned by Johan:
> > Can you try some tests without svn, for instance set up apache to
> > serve a simple static page protected by client cert authentication,
> > and try to access that with that cert using opens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey,
- --- Loritsch, Berin wrote: ---
> This one client that is failing, are any of the other clients using the
> 0.9.8k version of OpenSSL?
Only this specific client. Our workstation computers still run with
Ubuntu hardy and the old 0.9.8g version
> Can you try some tests without svn, for instance set up
> apache to serve a simple static page protected by client cert
> authentication, and try to access that with that cert using
> openssl 0.9.8g vs. 0.9.8k?
> Or try to build an svn client on your new machine with
> openssl 0.9.8g instead
/1.4.2
> - openssl/0.9.8c
> - Debian/etch
>
> Versions of the software running on the client:
> - Ubuntu 10.04
> - svn/1.6.6
> - kernel 2.6.32
> - openssl/0.9.8k
>
> Even though this seems to be more of an ssl-error I thought maybe some
> of you guys have seen it in
ons of the software running on the Server:
- Apache/2.2.3
- svn/1.4.2
- openssl/0.9.8c
- Debian/etch
Versions of the software running on the client:
- Ubuntu 10.04
- svn/1.6.6
- kernel 2.6.32
- openssl/0.9.8k
Even though this seems to be more of an ssl-error I thought maybe some
of you guys have
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
(and 1.6.12) I get the following error:
>>
>> svn: MKCOL of
>> '/repos/asf/!svn/wrk/c357a0ad-6c6c-4225-bcba-af72cc55b7ee/wicket/common/site/trunk/_site/2009/12/21':
>> SSL negotiation failed: SSL error: parse tlsext
>> (https://svn.apache.org)
>>
>> T
too many files)
> to the Apache SVN repository using the collabnet SVN client 1.6.11
> (and 1.6.12) I get the following error:
>
> svn: MKCOL of
> '/repos/asf/!svn/wrk/c357a0ad-6c6c-4225-bcba-af72cc55b7ee/wicket/common/site/trunk/_site/2009/12/21':
> SSL negotiation
#x27;:
SSL negotiation failed: SSL error: parse tlsext
(https://svn.apache.org)
Things worthy of note:
- OSX snow leopard
- both 1.6.11 and 1.6.12 clients from collab.net give the same error
- I'm based in the EU (Netherlands), so I go through the EU proxy
I've split up the commit to
40 matches
Mail list logo
