Jamin W. Collins a écrit :
I've just tested this on a bare Debian 4.0 installation. Installed only
jabber-1.4.3-3.3, created a self signed SSL certificate, and made the
minimal changes necessary to configure the server to use the certificate
and communicate with other servers.
Hello,
a first comment : there is no ssl configuration in my jabber.xml
If you still have your test installation, could you try to disable ssl
in your configuration and see if it still works ?
I then added my normal jabber account to the contact list of my new user
on the test system. Both accounts are connected to their respective
servers via SSL and I'm able to pass messages back and forth between them.
I'll try to setup a test server ASAP and test a brand new temporary
installation. If that bare installation works, I'll try to isolate what
part of its configuration makes my production setup choke on s2s
communications.
For those experiencing this problem, are you also running any
transports? If so, which one(s)? Can you try disabling all transports
and test just the core jabber server using the 1.4.3-3.3 package?
The only thing I have in <browse> is jud, nothing else.
Stay tuned for more info,
--
Rémi
