[Operators] Issues connecting to jabber.co.za

Tue Oct 14 06:56:31 CDT 2008

On Tue, Oct 14, 2008 at 1:46 PM, David Horwitz <david.horwitz at uct.ac.za>wrote:

> You can try connect to our server (uct.ac.za) which has those setting (tls
> optional + allow self signed dialback). We also get a secure connection with
> jabber.org & have a thawte cert...
>

Interesting:

14 13:49:20 [39] [137.158.155.14, port=3585] checking dialback verification
from uct.ac.za: sending valid
14 13:49:20 [21] [137.158.155.14, port=5269] outgoing route '/uct.ac.za' is
now valid, TLS negotiated
14 13:49:33 [40] [137.158.155.14, port=3587] incoming route '/uct.ac.za' is
now valid

why would I get TLS in one direction only - I wonder.

On Tue, Oct 14, 2008 at 1:22 PM, lzby <lzby.3h9q0b at no-mx.jabberforum.org>
 wrote:
>
> I am the admin of the jabber.co.za server. We are using Openfire 3.6.0a
> currently.

With additional testing I _can_ connect to jabber.co.za, but only if I
specify a client certificate.  It can be anything, even self-signed for the
wrong name, but it must be present.  This could be a bug in 3.6.0a perhaps?

-- 
- Norman Rasmussen
- Email: norman at rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.jabber.org/pipermail/operators/attachments/20081014/c3c40e77/attachment.htm 