Re: Porting the latest gossip to FreeBSD
Joe Marcus Clarke <[email protected]> Sun, 03 Aug 2008 17:20:38 -0400
| Newsgroups | gmane.comp.gnome.gossip.devel |
|---|---|
| Organization | MarcusCom, Inc. |
| Message-ID | <[email protected]> |
--===============0992196541== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Di0uUlBhMRee8jn/Qoqp" --=-Di0uUlBhMRee8jn/Qoqp Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-08-03 at 21:45 +0100, Martyn Russell wrote: Thanks for your reply. > > 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? I saw it in the working 0.28. FreeBSD doesn't have an NM port yet. >=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. It does. 0.26, 0.27, and 0.28 want to use 5223, but 0.29 and 0.31 want to use 5222. Neither port authenticates successfully in 0.29 and 0.31. >=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? Well, it's all hashed, so it doesn't really tell me what it's really sending: *** Socket library initialising... *** Connecting to: jabber.org:5223 *** SRV lookup disabled for jabber.org Going to connect to jabber.org:5223 Trying 208.68.163.220 port 5223... Connection success (2). *** Setting up SSL... *** GNUTLS negotiated compression: DEFLATE SEND: ----------------------------------- <?xml version=3D'1.0' encoding=3D'UTF-8'?> ----------------------------------- *** Sending stream header SEND: ----------------------------------- <stream:stream version=3D"1.0" xmlns=3D"jabber:client" xmlns:stream=3D"http://etherx.jabber.org/streams" to=3D"jabber.org" id=3D"4360577850"> ----------------------------------- RECV [168]: ----------------------------------- '<?xml version=3D'1.0'?><stream:stream xmlns=3D'jabber:client' xmlns:stream=3D'http://etherx.jabber.org/streams' id=3D'2193159157' from=3D'jabber.org' version=3D'1.0' xml:lang=3D'en'>' ----------------------------------- *** Read: 168 chars LM-PARSER: ATTRIBUTE: xmlns =3D jabber:client LM-PARSER: ATTRIBUTE: xmlns:stream =3D http://etherx.jabber.org/streams LM-PARSER: ATTRIBUTE: id =3D 2193159157 LM-PARSER: ATTRIBUTE: from =3D jabber.org LM-PARSER: ATTRIBUTE: version =3D 1.0 LM-PARSER: ATTRIBUTE: xml:lang =3D en LM-PARSER: Trying to close node: stream:stream LM-PARSER: Have a new message *** New message with type=3D"stream:stream" from: jabber.org *** XMPP 1.0 stream received: 2193159157 RECV [220]: ----------------------------------- '<stream:features><mechanisms xmlns=3D'urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism= ><mechanism>PLAIN</mechanism></mechanisms><register xmlns=3D'http://jabber.= org/features/iq-register'/></stream:features>' ----------------------------------- *** Read: 220 chars LM-PARSER: ATTRIBUTE: xmlns =3D urn:ietf:params:xml:ns:xmpp-sasl LM-PARSER: Trying to close node: mechanism LM-PARSER: Trying to close node: mechanism LM-PARSER: Trying to close node: mechanisms LM-PARSER: ATTRIBUTE: xmlns =3D http://jabber.org/features/iq-register LM-PARSER: Trying to close node: register LM-PARSER: Trying to close node: stream:features LM-PARSER: Have a new message *** New message with type=3D"stream:error" from: unknown LM-SASL: Stream features received SEND: ----------------------------------- <auth mechanism=3D"DIGEST-MD5" xmlns=3D"urn:ietf:params:xml:ns:xmpp-sasl" id=3D"134986749423"></auth> ----------------------------------- RECV [148]: ----------------------------------- '<challenge xmlns=3D'urn:ietf:params:xml:ns:xmpp-sasl'>bm9uY2U9IjEwNzU0Mzk4MjEiLHFvcD0i= YXV0aCIsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=3D</challenge>' ----------------------------------- *** Read: 148 chars LM-PARSER: ATTRIBUTE: xmlns =3D urn:ietf:params:xml:ns:xmpp-sasl LM-PARSER: Trying to close node: challenge LM-PARSER: Have a new message *** New message with type=3D"challenge" from: unknown SEND: ----------------------------------- <response xmlns=3D"urn:ietf:params:xml:ns:xmpp-sasl" id=3D"264451813363">dXNlcm5hbWU9IkZyZWVCU0RNYXJjdXMiLHJlYWxtPSJqYWJiZXIub3J= nIixkaWdlc3QtdXJpPSJ4bXBwL2phYmJlci5vcmciLG5vbmNlPSIxMDc1NDM5ODIxIixuYz0wMD= AwMDAwMSxjbm9uY2U9IkNaVWZOSkZqQllSNE5jSzBGOXdHYi9WMDR0ZXhFVW5KaUFFQzYvTUV6d= 2M9Iixxb3A9YXV0aCxjaGFyc2V0PXV0Zi04LHJlc3BvbnNlPTNlZDk1ZjQ5MGNhYzNmYTUzNGUx= MjBkZTgwYWM5YWMw</response> ----------------------------------- RECV [77]: ----------------------------------- '<failure xmlns=3D'urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure>' ----------------------------------- *** Read: 77 chars LM-PARSER: ATTRIBUTE: xmlns =3D urn:ietf:params:xml:ns:xmpp-sasl LM-PARSER: Trying to close node: not-authorized LM-PARSER: Trying to close node: failure LM-PARSER: Have a new message *** New message with type=3D"failure" from: unknown LM-SASL: sasl_failure_cb: SASL authentication failed: unknown reason*** SASL authentication failed, closing connection *** Disconnecting from: jabber.org:5223 SEND: ----------------------------------- </stream:stream> ----------------------------------- Freeing up IOChannel and file descriptor How can I see what username and password is actually being sent? Where could I add some debug code to print that? Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-Di0uUlBhMRee8jn/Qoqp 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) iEYEABECAAYFAkiWISUACgkQb2iPiv4Uz4csHACfVmCmeinBn/krDHs8FtWMSONi WGEAnRp8Oa4xKat2XqMav90MI7UQD3kJ =54H+ -----END PGP SIGNATURE----- --=-Di0uUlBhMRee8jn/Qoqp-- --===============0992196541== 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 --===============0992196541==--