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
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 problem. :-(
I will take this up with the server admionistrator, as
Thanks for your help Stefan.
I tried your suggestions (using the 1.6.11 svn CLI on windows and
specifying the --non-interactive --trust-server-cert options), but
neither worked.
Fortunately, when I tried the latest svn CLI (1.6.15), it functioned
just like the linux CLI (asking me to accept the c
On Thu, Dec 16, 2010 at 09:34:05AM -0500, Nick wrote:
> Hi all,
>
> At some point in the last year I stopped being able to access my SVN
> repository remotely via https using the SVN CLI and TortoiseSVN on
> Windows. Unfortunately since I hadn't used svn on my windows machine
> for a long time (m
> 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
On Mon, Oct 11, 2010 at 4:25 PM, Bernd May wrote:
> Hey all,
>
> I have a curious problem that I seem unable to find precedence for.
>
>
> The Error:
>
> --- on the client side ---
> svn up
> svn: OPTIONS of 'https:///svn/': SSL
> handshake failed: SSL alert received: Decode error (https://)
>
> -
10 matches
Mail list logo
