[Wocky] How much does AdiumX 1.2.1 fix?

[Greg Hudson]

On Fri, 2008-01-25 at 00:58 -0500, Ken Raeburn wrote:
> It appears that I need to specify the "connect host" of  
> jabber.mit.edu, *and* use my password, to sign on to our main jabber  
> server.  Once I do that, I get in okay.  If I don't have a connect  
> host specified, I'm repeatedly prompted for my password as if I'd  
> given an incorrect one.  So, GSSAPI authentication still seems to be  
> a no-go, but I can sign on with the latest version much like with  
> 1.1.4.  I'm not sure why omitting the connect host causes even  
> password authentication to break...

If you specify a connect host, GSSAPI authentication fails earlier,
because of the bug where libpurple selects the XMPP domain as the server
FQDN if a connect host is specified.  Presumably in this case the
fallback logic to using a password works.

If you do not specify a connect host, GSSAPI authentication fails later,
because of the server bug where authorization fails if the client
doesn't choose an authz name.  (The server upgrade is blocking on
scheduling issues with NIST, and is still scheduled for "soon".)  In
this case the fallback logic to using a password does not appear to
work; I guess the client asks for a password, retries the connect,
re-attempts GSSAPI auth, and repeats.