[33410] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Instant Messaging client-server solution?

daemon@ATHENA.MIT.EDU (Jaap Winius)
Fri May 20 13:03:43 2011

Message-ID: <20110520151124.96093ps15h0wm2ww@bitis.umrk.nl>
Date: Fri, 20 May 2011 15:11:24 +0200
From: Jaap Winius <jwinius@umrk.nl>
To: kerberos@mit.edu
In-Reply-To: <1305751224.2681.3.camel@mentor.gurulabs.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

Quoting Dax Kelson <dkelson@gurulabs.com>:

> We used Pidgin and OpenFire in our office. Works well. Was pretty
> straightforward to configure.

Really? It doesn't look so easy to me. The docs for both Openfire and  
Pidgin make no mention of GSSAPI or Kerberos. Most of the discussions  
on this subject seem to be a couple of years old or have to do with  
Windows environments.

Then there's the Stanford IT Lab Blog article on Openfire. It's over  
two years old, but seems to work with Openfire 3.7.0 on my system.  
However, I wasn't able to get Pidgin to communicate with it. Also,  
when I break the configuration, e.g. by renaming gss.conf and  
restarting the daemon, Openfire gives no errors and behaves the same  
as before. So, for all I know it's ignoring the additional SASL/GSSAPI  
configuration.

Cheers,

Jaap
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post