Failed connect to msn (nss handshake failed -8128)

[Marc Brevoort]

After ICQ connect no longer worked a few days ago,
I tried building pidgin from source (after doing a
sudo apt-get build-deps gaim). This worked, but without
MSN support.

As a new package became available, I did a fresh install from the repository.
However, from home I keep not managing to connect to MSN,
even after a 'complete' remove and re-install from the apt repository.
I don't have any troubles connecting to MSN elsewhere.
No firewall (just a NAT router).

The debug window shows

(17:57:57) account: Connecting to account <email address hidden>
(17:57:57) connection: Connecting. gc = 0x8736ce8
(17:57:57) msn: new httpconn (0x8736678)
(17:57:57) dns: DNS query for 'gateway.messenger.hotmail.com' queued
(17:57:57) msn: C: NS 000: VER 1 MSNP9 MSNP8 CVR0
(17:57:57) dns: Created new DNS child 7121, there are now 1 children.
(17:57:57) dns: Successfully sent DNS request to child 7121
(17:57:57) dns: Got response for 'gateway.messenger.hotmail.com'
(17:57:57) dnsquery: IP resolved for gateway.messenger.hotmail.com
(17:57:57) proxy: Attempting connection to 207.46.96.154
(17:57:57) proxy: Connecting to gateway.messenger.hotmail.com:80 with no proxy
(17:57:57) proxy: Connection in progress
(17:57:57) proxy: Connected to gateway.messenger.hotmail.com:80.
(17:57:57) msn: S: NS 000: VER 1 MSNP9 MSNP8 CVR0
(17:57:57) msn: C: NS 000: CVR 2 0x0409 winnt 5.1 i386 MSNMSGR 6.0.0602 MSMSGS <email address hidden>
(17:57:57) util: Writing file prefs.xml to directory /home/mrjb/.purple
(17:57:57) util: Writing file /home/mrjb/.purple/prefs.xml
(17:57:57) msn: S: NS 000: CVR 2 8.1.0178 8.1.0178 8.1.0178 http://msgruser.dlservice.microsoft.com/download/5/6/4/5646481F-33EF-4B08-AF00-4904F7677B89/EN/Install_WLMessenger.exe http://messenger.msn.com
(17:57:57) msn: C: NS 000: USR 3 TWN I <email address hidden>
(17:57:58) msn: S: NS 000: USR 3 TWN S ct=1215536240,rver=5.5.4177.0,wp=FS_40SEC_0_COMPACT,lc=1033,id=507,ru=http:%2F%2Fmessenger.msn.com,tw=0,kpp=1,kv=4,ver=2.1.6000.1,rn=1lgjBfIL,tpf=b0735e3a873dfb5e75054465196398e0
(17:57:58) dns: DNS query for 'nexus.passport.com' queued
(17:57:58) dns: Created new DNS child 7126, there are now 1 children.
(17:57:58) dns: Successfully sent DNS request to child 7126
(17:57:58) dns: Got response for 'nexus.passport.com'
(17:57:58) dnsquery: IP resolved for nexus.passport.com
(17:57:58) proxy: Attempting connection to 65.54.179.216
(17:57:58) proxy: Connecting to nexus.passport.com:443 with no proxy
(17:57:58) proxy: Connection in progress
(17:57:58) proxy: Connected to nexus.passport.com:443.

(17:57:58) nss: Handshake failed (-8128)

(17:57:58) msn: C: NS 000: OUT
(17:57:58) account: Disconnecting account 0x86dde50
(17:57:58) connection: Disconnecting connection 0x8736ce8
(17:57:58) msn: destroy httpconn (0x8736678)
(17:57:58) connection: Destroying connection 0x8736ce8

I suspect the problem is with the handshake. Online, I've seen
other people with failed handshakes but with a different error code.
This one seems SSL related.

I've got the gnutls library+dev package so I don't think that is
the problem.

Any ideas?

[Marc Brevoort (kleinebre)]

Removing and re-installing did not work.
What did work, however, was re-compiling with GNUTLS enabled and NSS disabled.

I pretty much followed this:
http://ubuntuforums.org/showthread.php?t=404508

Except I used
./configure --prefix=/usr --enable-gnutls=yes --enable-nss=no

So that it would not try to use both. It's working again now!

[Magnus S (magnuss)]

Hi, thanks for the report. It sounds like you fixed this issue already, right?

Unfortunately this means that we cant fix this bug, because we cant get the information needed, so i am closing it now. Please reopen if you can reproduce the bug.

Thanks again.
//magnus

[Marc Brevoort (kleinebre)]

> Subject: [Bug 246667] Re: Failed connect to msn (nss handshake failed -8128)
>
> Hi, thanks for the report. It sounds like you fixed this issue already,
> right?

Yes, the recompile solved the problem. Probably had to do with
having both libraries available *and* having both enabled at
compile time.

In the meantime I've changed computer (clean OS install)
and the problem has not reoccurred- so my guess is that the
problem was simply caused by a very specific upgrade scenario.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/