[ejabberd] S2S Problems to some Openfire servers

Nikolaus Polak nik at np-edv.at
Tue Feb 3 14:06:13 MSK 2009

----- "Badlop" <badlop at gmail.com> wrote:
> There are two possibilities:
> A) A problem in recent Openfire breaks his s2s STARTTLS
> B) A problem in ejabberd s2s STARTTLS is visible now because recent
> Openfire is more strict.
I tried to reproduce the problem with an openfire installation, it
seems that when "Server Connection Security" is set on "Required" in
Openfire, no s2s is possible. Sorryly the logs of Openfire are also
not very clear to me.
When "Server Connection Security" is set to "Optional", s2s
connections are working. The setting "Accept self-signed certificates.
Server dialback over TLS is now available." in Openfire doesn't help
when "Server Connection Security" is set to "Required".

Nikolaus Polak - http://nplog.0nl1ne.at - xmpp:nik(at)linuxlovers.at

More information about the ejabberd mailing list