Christof,
I had the same problem, luckily I ran on a test server. I could not even
login with my client.
There has been a change in sx/ssl.c line 899. The line now reads
ctx = SSL_CTX_new(TLSv1_2_method());
This means that it will support TLS v1.2 only. Connections using SSLv3
or TLS v1.1
If you are interested you can try the changes I made in
http://suchat.org/sx/ssl.c
For protocols TLS v1.0, v1.1 and v1.2.
Carlos
El 26/11/13 10:11, Eric Koldeweij escribió:
Christof,
I had the same problem, luckily I ran on a test server. I could not
even login with my client.
There has
Dnia 2013-11-26, wto o godzinie 07:40 +0100, Christof Meerwald pisze:
I tried upgrading from 2.2.17 to 2.3.0 yesterday, but that left me
with a broken server. The s2s component now just connects to a remote
server, switches the stream to TLS, gets the certificate, disconnects
and immediately
On Tue, 26 Nov 2013 07:40:14 +0100
Christof Meerwald wrote:
On Mon, 18 Nov 2013 17:18:07 +0100, Tomasz Sterna wrote:
Next jabberd2 release is finally available.
Get 2.3.0 release at GitHub: https://github.com/jabberd2/jabberd2/releases
I tried upgrading from 2.2.17 to 2.3.0 yesterday,
Next jabberd2 release is finally available.
Get 2.3.0 release at GitHub: https://github.com/jabberd2/jabberd2/releases
This release packs many new features and load of bugfixes.
Also introducing Semantic Versioning scheme
and TLS Everywhere recommendation.
Many, many thanks to all
