Re: Porting the latest gossip to FreeBSD

--===============0907893741==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pW7oijvCIGRCIn0JOk7+"


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

On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote:
> Joe Marcus Clarke wrote:
>=20
> Hi :)
>=20
> > 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 authenticatio=
n
> > failed (error 4).  If I downgrade to gossip 0.28, everything works.
>=20
> OK.
>=20
> First, thanks for the patch!
>=20
> > 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:
> >=20
> > 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'
> >=20
> > The NetworkManager error doesn't appear to be fatal, and I get this wit=
h
> > 0.28 as well. =20
>=20
> The network manager issue there shouldn't be a problem. But I wonder if
> it is part of the problem?
>=20
> > 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.
>=20
> Gossip should switch between ports for you. But for old SSL
> authentication, you want to use port 5223. Otherwise port 5222 should wor=
k.
>=20
> > 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.
>=20
> Hmm, interesting. I can connect to my jabber.org account fine here.
> If you run Gossip with LM_DEBUG=3Dall, does it give you any more informat=
ion?

I found the problem.  It is due to ebook support.  This links gossip to
e-d-s which links to NSS (for SSL support).  There is a symbol conflict
between GnuTLS and NSS on FreeBSD.  If loudmouth is linked with
-Wl,-Bsymbolic, the problem goes away, and gossip can once again
authenticate and have working ebook support.

Joe

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

--=-pW7oijvCIGRCIn0JOk7+
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)

iEYEABECAAYFAkiWO28ACgkQb2iPiv4Uz4elsQCfU4aRuPqIYNH7eJkqz8OiaIQK
MQMAnRrOS2KhkT0oU0j1YHDL08S88hEn
=M0oV
-----END PGP SIGNATURE-----

--=-pW7oijvCIGRCIn0JOk7+--


--===============0907893741==
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

--===============0907893741==--