Yes I'm sure. In fact I've just tested it myself. I get a "Policy Violation" error if I try to login unencrypted on port 5222. Are you sure that the connection is unencrypted?
The ip inside '<ip></ip>' is the ip on which jabberd will bind on. If you specify '0.0.0.0' then it'll listen on any ip address (and any interface). Our server has several ip addresses and we spread our services amongst them, therefore we tell jabberd specifically on which ip it has to listen. Here's a network capture of the failed connection, I used psi and jabberd2 2.2.5 to test. <!-- OUT --> <?xml version="1.0"?> <stream:stream xmlns:stream="http://etherx.jabber.org/streams"; version="1.0" xmlns="jabber:client" to="domain.org" xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace"; > <!-- IN --> <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='domain.org' version='1.0' id='9047rcafrfovriv8cyke2wd1sn6a3m1dm5leiwua'><stream:features xmlns:stream='http://etherx.jabber.org/streams'><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'><required/></starttls><auth xmlns='http://jabber.org/features/iq-auth'/><register xmlns='http://jabber.org/features/iq-register'/></stream:features> <!-- OUT --> <iq type="get" to="domain.org" id="auth_1" > <query xmlns="jabber:iq:auth"> <username>shino</username> </query> </iq> <!-- IN --> <stream:error xmlns:stream='http://etherx.jabber.org/streams'><policy-violation xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text xmlns='urn:ietf:params:xml:ns:xmpp-streams'>STARTTLS is required for this stream</text></stream:error> On Mon, 13 Apr 2009 18:27:29 +0200 - - <[email protected]> wrote: > > Hi, > ---------------------------------------- > > Date: Mon, 13 Apr 2009 13:31:45 +0200 > > From: [email protected] > > To: [email protected] > > Subject: Re: force encrypted connections (either TLS or SSL)? > > > > Yes it's possible, here's the significant part of our c2s.xml: > > > > > > require-starttls='true' > > pemfile='/etc/jabber/server.pem'>domain.org > > > > 134.36.75.196 > > 5222 > > > > 5223 > > /etc/jabber/server.pem > > > > are you really sure? I have set-up my c2s.xml the same way (although > I have left 0.0.0.0 the default way, because I don't know what this > options is for) and iChat 4 (like kopete only capable of doing SSL) > seems to login unencrypted (port 5222, SSL deactivated). *Huhhh*? > _________________________________________________________________ > http://redirect.gimas.net/?n=M0904xWLCalendar2 Keinen Termin mehr > verpassen! Mit Windows Live Kalender. -- To unsubscribe send a mail to [email protected]
