[jdev] Looking for servers that support XEP-0138 on s2s
dave at cridland.net
Wed Mar 4 07:14:58 CST 2009
On Wed Mar 4 12:58:15 2009, Norman Rasmussen wrote:
> SSL handshake has read 4027 bytes and written 456 bytes
> New, TLSv1/SSLv3, Cipher is AES256-SHA
> Server public key is 2048 bit
> Compression: NONE
> Expansion: NONE
> Protocol : TLSv1
> Cipher : AES256-SHA
> Key-Arg : None
> Start Time: 1236171444
> Timeout : 300 (sec)
> Verify return code: 20 (unable to get local issuer certificate)
That simply means you're using a SSLv2 handshake. Using an SSLv3 or
TLS handshake *will* give you compression, assuming your OpenSSL is
built right, which it probably is.
> No features, so XEP-0138 isn't being offered.
> As far as I know there are no server implementations that offer
> XEP-0138 via
> s2s at this point in time.
dave.cridland.net should be, Isode M-Link has supported it for some
time - more or less from its initial release. I didn't realise it
wasn't popular on S2S, so it's had little interop testing, but it
ought to work both incoming and outgoing.
(We also do TLS compression, although there's some known bugs there
in current releases, but I tend to run somewhat trunky code, so it'll
Note that it shouldn't offer XEP-0138 if TLS compression is enabled,
but I admit to not having tested that for a while.
Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
More information about the JDev