Dr. Stephen Henson wrote:
openssl s_client -connect xxx.org:443
and it should say if secure renegotiation is supported in
the output.
Thanks for the tip! I tried, but I am afraid I cannot tell
whether it is the case or not, based on this output. I tried
on google.com:443 as
Hi,
I am using openssl from within neon, itself used from within
Subversion. During an svnsync, I receive the following error
message:
svnsync: PROPFIND of '/svn/xxx': SSL negotiation failed: SSL
error: parse tlsext (https://xxx.org)
If I am right, this message comes from openssl
Hi,
I am using openssl from within neon, itself used from within
Subversion. During an svnsync, I receive the following error
message:
svnsync: PROPFIND of '/svn/xxx': SSL negotiation failed: SSL
error: parse tlsext (https://xxx.org)
If I am right, this message comes from openssl
On Wed, Apr 07, 2010, Florent Georges wrote:
Hi,
I am using openssl from within neon, itself used from within
Subversion. During an svnsync, I receive the following error
message:
svnsync: PROPFIND of '/svn/xxx': SSL negotiation failed: SSL
error: parse tlsext (https
Dr. Stephen Henson wrote:
Thanks for your fast response!
That looks like it is only part of the actual error code.
That's all I have. I guess either Subversion or Neon truncates
the error message.
I suspect it is because the server doesn't support secure
renegotiation. You can check
On Wed, Apr 07, 2010, Florent Georges wrote:
Dr. Stephen Henson wrote:
Thanks for your fast response!
That looks like it is only part of the actual error code.
That's all I have. I guess either Subversion or Neon truncates
the error message.
I suspect it is because the server
