These are the changes I made
jabberd-2.3.0/sx/ssl.c
660 - SSL_set_ssl_method(sc->ssl, TLSv1_2_client_method());
660 + SSL_set_ssl_method(sc->ssl, TLSv1_client_method());
...
899 - ctx = SSL_CTX_new(TLSv1_2_method());
899 + ctx = SSL_CTX_new(SSLv23_method());
...
757 SSL_set_accept_state(sc->ssl);
758 + SSL_set_options(sc->ssl, SSL_OP_NO_SSLv3);
El 26/11/13 11:45, Tomasz Sterna escribió:
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 connects again.
I guess the network is not that ready for 'TLS Everywhere' [1] yet.
Maybe it is worth releasing 2.2.18 without that change.
[1] https://github.com/jabberd2/jabberd2/commit/ad9ead7816
