On Tue, Oct 14, 2008 at 1:46 PM, David Horwitz <[EMAIL PROTECTED]>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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
