I guess all of them need to be reported to the subversion people though.
I assume they are not directly related to libserf.
Thanks again for the fast help, hope to see that fix in downstream
packes soon :)
--
Technische Universität Berlin - FGINET
Bernd May
System Administration
Sekr. TEL
r libraries?
If anyone could point me to a way to further debug this or a solution,
I'd be very gracious
--
Technische Universität Berlin - FGINET
Bernd May
System Administration
Sekr. TEL 16
Ernst-Reuter-Platz 7
10587 BERLIN
GERMANY
Mobile: 0160/90257737
E-Mail: be...@inet.tu-berlin.
ertificate but the same software versions and it works.
So I guess the problem is this specific client certificate though I
still do not know what specifically.
thanks
- --
Bernd May
System Administration
Technische Universität Berlin
An-Institut Deutsche Telekom Laboratories
FG Intelligente Netze
Sekr. T
rks from all our regular workstations.
So this Problem seems to be subversion specific.
I will setup a test server on thursday with a current version of apache,
subversion and openssl and test if the failing client still has problems.
- --
Bernd May
System Administration
Technische Universität Ber
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://)
--- on the server side from apache error.log ---
[debug] ssl_engine_kerne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am currently trying to configure my svn client so it automagically
uses my client ssl certificate to authenticate to our svn server.
The documentation states that one simply should edit the configuration
in .subversion/servers by adding a new group,
