[jdev] PyMSNt & Jabber2 & Who knows what...

[Javier Villavicencio]

Hi all, I've recently upgraded our server to jabber2, we had a strange 
"authentification" scheme that worked fine with old jabber1.4.x and 
xdb_auth_cpile.pl perl module, since this wasn't compatible with jabber2 
i did some (cut&paste) perl work on the pipe-auth thing of jabberd2 and 
everyone logged in fine to jabber.

The problem (now) is: as far as I've readed, with PyMSNt I wouldn't need 
anything else to add to the router configuration (other than same port, 
same secret) to make it work, but after the upgrade, no one can connect 
to MSN again (i mean "the transport").

This is the last "message" from jabber server to the debug window of 
Exodus (we're using it only compiled with our default language, that's 
the only modification to the sources, and it was working fine before the 
upgrade :+P)

SENT: <iq id="jcl_15" to="msn.migraciones.gov.ar" type="get"><query 
xmlns="http://jabber.org/protocol/disco#info"/></iq>
RECV: <iq xmlns='jabber:client' from='msn.migraciones.gov.ar' 
type='result' id='jcl_15' to='javierv at migraciones.gov.ar/DNM'><query 
xmlns='http://jabber.org/protocol/disco#info'><identity 
category='gateway' type='msn' name='MSN Transport'/><identity 
category='conference' type='text' name='MSN Transport 
Chatrooms'/><feature var='http://jabber.org/protocol/disco'/><feature 
var='jabber:iq:version'/><feature var='jabber:iq:register'/><feature 
var='jabber:iq:gateway'/><feature 
var='http://jabber.org/protocol/muc'/></query></iq>

which seems fine, and in the debuglog of PyMSNt:

10/05/04 - 19:29:38 - MSNConnection: "thepaya_ at hotmail.com" initialised
10/05/04 - 19:30:35 - Sessions:
10/05/04 - 19:30:35 -   javierv at migraciones.gov.ar
10/05/04 - 19:30:48 - NotificationClient: "thepaya_ at hotmail.com" lost 
connection with MSN servers
10/05/04 - 19:31:04 - MSNConnection: "thepaya_ at hotmail.com" destroyed

At this hours, being myself the only user logged in, these messages 
repeat in an endless loop (from initialized to destroyed).

Also an 'ngrep' to the port 1863 (MSN port) reveals the next things:
(a bit stripped:)

dnmmail src # ngrep port 1863
interface: eth0 (200.55.54.64/255.255.255.248)
filter: ip and ( port 1863 )
T 200.55.54.70:57321 -> 207.46.104.20:1863 [AP]
  VER 1 MSNP8 CVR0..
T 207.46.104.20:1863 -> 200.55.54.70:57321 [AP]
  VER 1 MSNP8 CVR0..
T 200.55.54.70:57321 -> 207.46.104.20:1863 [AP]
  CVR 2 0x0409 win 4.10 i386 MSNMSGR 5.0.0544 MSMSGS thepaya_ at hotmail.com..
T 207.46.104.20:1863 -> 200.55.54.70:57321 [AP]
  CVR 2 6.2.0137 6.2.0137 5.0.0527 
http://download.microsoft.com/download/0/9/a/09a79e99-f2c8-493
  3-9797-77e88836bb52/Setup9X.EXE http://messenger.msn.com..
T 200.55.54.70:57321 -> 207.46.104.20:1863 [AP]
  USR 3 TWN I thepaya_ at hotmail.com..
T 207.46.104.20:1863 -> 200.55.54.70:57321 [AP]
  XFR 3 NS 207.46.107.69:1863 0 207.46.104.20:1863..
T 200.55.54.70:57322 -> 207.46.107.69:1863 [AP]
T 200.55.54.70:57322 -> 207.46.107.69:1863 [AP]
  VER 1 MSNP8 CVR0..
T 207.46.107.69:1863 -> 200.55.54.70:57322 [AP]
  VER 1 MSNP8 CVR0..
T 200.55.54.70:57322 -> 207.46.107.69:1863 [AP]
  CVR 2 0x0409 win 4.10 i386 MSNMSGR 5.0.0544 MSMSGS thepaya_ at hotmail.com..
T 207.46.107.69:1863 -> 200.55.54.70:57322 [AP]
  CVR 2 6.2.0137 6.2.0137 5.0.0527 
http://download.microsoft.com/download/0/9/a/09a79e99-f2c8-493
  3-9797-77e88836bb52/Setup9X.EXE http://messenger.msn.com..
T 200.55.54.70:57322 -> 207.46.107.69:1863 [AP]
  USR 3 TWN I thepaya_ at hotmail.com..
T 207.46.107.69:1863 -> 200.55.54.70:57322 [AP]
  USR 3 TWN S 
lc=1033,id=507,tw=40,fs=1,ru=http%3A%2F%2Fmessenger%2Emsn%2Ecom,ct=1097015751,kpp=1
  ,kv=5,ver=2.1.6000.1,tpf=59b0a2cb3ee48d530290f5ba1849978b..

What can I see here is that the first challenge to MSN (server 
redirection) is done well, but when it turns to start the second 
challenge (password authenthication??) PyMSNt doesn't reply anymore, and 
then, after a timeout (?) the connection is closed.

Searching and searching and searching about this, i've found that the 
"old" msn-transport can just "die" here if there is a problem with the 
'Curl' library (wich, ehem, was working well before jabber2) is this 
really related to Curl? Does Twisted/PyMSNt makes use of the Curl 
library? or there is another package (maybe in python) related to this 
kind of "transaction" with the MSN servers?

For more information my system is a Gentoo 2004.2 "synced everyday 
(tm)", I'm running:

jabberd-2.0-r1    (jabberd2.0s3)
curl-7.12.0-r2
python-2.3.3-r1
twisted-1.3.0-r2    (installed from portage with the patch from PyMSNt 
applied by custom ebuild)

I want to go home today :'( please any help is welcome :+)

Salu2.

Javier Villavicencio
Dirección Nacional de Migraciones
Ministerio del Interior
Gobierno de la Nación - República Argentina.