Porting the latest gossip to FreeBSD

Joe Marcus Clarke <[email protected]> Sun, 03 Aug 2008 16:35:03 -0400
Newsgroups gmane.comp.gnome.gossip.devel
Organization MarcusCom, Inc.
Message-ID <[email protected]>
--===============0180152450==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-N2UVrDZjIExP0m5M9rzm"


--=-N2UVrDZjIExP0m5M9rzm
Content-Type: multipart/mixed; boundary="=-sghRKM1wdoWwOATPVbTg"


--=-sghRKM1wdoWwOATPVbTg
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I have been trying to update our gossip port from 0.26 to 0.31.
Loudmouth 1.4.1 is successfully installed, and gossip 0.31 builds fine
except for one small patch (attached).  The problem is, gossip 0.31
refuses to authenticate with jabber.org.  I always get an authentication
failed (error 4).  If I downgrade to gossip 0.28, everything works.

If I then upgrade to 0.29, I am no longer able to login again.  I am
using gnome-keyring, and I can see in my keyring that the password is
successfully stored.  Debug from 0.31 shows:

Jabber: Untrusted certificate
Jabber: Connection open!
Jabber: Attempting to use JabberID:'[email protected]'
Jabber: Disconnecting for account:'Test'
Session: Protocol disconnecting for account:'Test'
Sound: Protocol disconnecting for account:'Test'
Session: Protocol disconnected (after 0.00 seconds)
AppSession: Disconnected account:'Test'
DBUS: Failed to complete 'state' request. The name
org.freedesktop.NetworkManager was not provided by any .service files
JabberUtils: Error:4->'Authentication failed.'
Session: Error:4->'Authentication failed.'
AppSession: Error for account:'Test'

The NetworkManager error doesn't appear to be fatal, and I get this with
0.28 as well.  Nothing else is different settings-wise between 0.28 and
0.31.  I'm using the resource Home, and I am using encryption.  I've
tried both ports 5222 and 5223.  The server is jabber.org.

Both gossip 0.28 and pidgin can connect with this account and password.
Creating a new account in gossip 0.31 also does not work.  Any clue as
to what the problem may be?  Is there any additional troubleshooting I
can do?  A sniffer isn't helpful as this is all encrypted.

Joe

--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-sghRKM1wdoWwOATPVbTg
Content-Disposition: attachment; filename=patch-libloudermouth_lm-bs-listener.c
Content-Transfer-Encoding: base64
Content-Type: text/x-patch; name=patch-libloudermouth_lm-bs-listener.c;
	charset=ISO-8859-1

LS0tIGxpYmxvdWRlcm1vdXRoL2xtLWJzLWxpc3RlbmVyLmMub3JpZwkyMDA4LTA4LTAzIDE0OjM4
OjM3LjAwMDAwMDAwMCAtMDQwMA0KKysrIGxpYmxvdWRlcm1vdXRoL2xtLWJzLWxpc3RlbmVyLmMJ
MjAwOC0wOC0wMyAxNDozODo1MC4wMDAwMDAwMDAgLTA0MDANCkBAIC0yNyw2ICsyNyw3IEBADQog
I2luY2x1ZGUgPGdsaWIuaD4NCiANCiAjaWZuZGVmIEdfT1NfV0lOMzINCisjaW5jbHVkZSA8c3lz
L3R5cGVzLmg+DQogI2luY2x1ZGUgPHN5cy9zb2NrZXQuaD4gDQogI2luY2x1ZGUgPG5ldGluZXQv
dGNwLmg+IA0KICNlbmRpZiAvKiBHX09TX1dJTjMyICovDQo=


--=-sghRKM1wdoWwOATPVbTg--

--=-N2UVrDZjIExP0m5M9rzm
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkiWFnUACgkQb2iPiv4Uz4cEugCgqyCmZ/YPQzYaSuWzAOX5raog
ZGgAnjIv9NecA+q0Yw5pIuNWOBktDmDN
=SY9i
-----END PGP SIGNATURE-----

--=-N2UVrDZjIExP0m5M9rzm--


--===============0180152450==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gossip-dev mailing list
[email protected]
http://lists.imendio.com/mailman/listinfo/gossip-dev

--===============0180152450==--