thanks for the detailed description, this was really helpful.
the pre-starttls strings clarifies the behaviour.
i am going to try to setup a second SM, one for guuk.eu and one for
xmpp.guuk.eu, this should solve my issue.
thanks again and greetings
-mog
I wouldn't say it's a bug. You didn't show us the complete configuration file,
but I am assuming
you did not configure jabberd2 to also serve "xmpp.guuk.eu", so when you try to
connect to "xmpp.guuk.eu"
jabberd2 doesn't know that it should also serve users for x...@xmpp.guuk.eu. If
you need that
i found the error by myself. IMHO this is a bug within jabberd2 not responding
to openssl s_client calls while using the FQDN instead of the domain part of
the JID. especially because some xmpp clients give you the ability to connect
to another host instead of your domain part of your JID.
wh
so, i checked my configuration, but i am stuck, no ideas anymore what is
missing or wrong.
that's the software i am using. jabberd2 from unstable and openssl from testing
(debian)
# dpkg --list jabberd2 openssl
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/hal
> what i expect is a dump of the certificate chain, like it is with all
> other protocols which are supported by openssl s_client.
> any ideas?
> Misconfigured server?
> With my server it works just fine...
> 23:34 ~ $ openssl s_client -CApath /etc/ssl/certs -starttls xmpp -connect
chrome.pl:522
Dnia 2015-05-08, pią o godzinie 22:47 +0200, Guenther Kuenzel pisze:
> what i expect is a dump of the certificate chain, like it is with all
> other protocols which are supported by openssl s_client.
> any ideas?
Misconfigured server?
With my server it works just fine...
23:34 ~ $ openssl s_clie
hi,
i am struggling with the command to test TLS capabilities of the jabberd2
server.
the command i am using is:
openssl s_client -CApath /etc/ssl/certs -starttls xmpp -connect
server.domain.tld:5222
but all i am getting is:
CONNECTED(0003)
what i expect is a dump of the certificate chain,
