Re: ANNOUNCE: Gossip 0.13
Paul van Tilburg <[email protected]>
| Newsgroups | gmane.comp.gnome.gossip.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 02, 2006 at 02:35:24PM +0200, Keywan Najafi Tonekaboni wrote: > Hi, > > Am Mittwoch, den 02.08.2006, 12:47 +0200 schrieb Paul van Tilburg: > > On Mon, Jul 31, 2006 at 07:03:39PM +0200, Keywan Najafi Tonekaboni wrote: > > > Hi, > > > > > > I built gossip and run it and couldn't connect to any account except > > > google talk anymore. The error is "Authentication failed". With gossip > > > 0.12 it's no problem. I test it with three different servers (from a > > > friend, at work, and on localhost). All the server are jabberd 1.x > > > servers. For the remote server I use SSL/TLS and on localhost no SSL. > > > > I have the same problem. However it seems to be architecture-related > > When I build & run Gossip CVS on x86 machines, it logs in fine. On > > PowerPC I get 'authorisation failed'. > > Did I said I run Ubuntu Dapper on a PowerPC? Which distribution/OS do > you use? I am using Debian GNU/Linux sid on PowerPC. > Yesterday I try to investigate with the help of Martyn to the problem. > Because of privacy issues I send my mails directly to Martyn. I did so too. :) > A summary: > > - It's not a wrong password etc problem, the same credentials are used > as before > - gossip 0.10.2 and 0.12 works fine, again with the same credentials and > on the same computer with the same environment (Ubuntu Dapper, loudmouth > 1.0.3-0ubuntu1) > - the problem is only with server, who authenticate via encrypted > passwords (<digest/>) instead of plain text (<password/>). > - It's not related to the server version. I test it with jabber.org and > jabber.ru, which use ejabberd, but asks for authentication via <digest/> > - Loudmouth seems not be responsible: loudmouth wasn't changed and > examples works fine. I concur with all the above posed observations. Paul -- Student @ Eindhoven | email: [email protected] University of Technology, The Netherlands | JID: [email protected] >>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181