[Pidgin] #3456: TLS handshake error(unexpected length packet) when recieving MSN contact list

[Pidgin]

#3456: TLS handshake error(unexpected length packet) when recieving MSN contact
list
--------------------------------------+-------------------------------------
 Reporter:  bsdunx                    |        Owner:  khc    
     Type:  defect                    |       Status:  closed 
Milestone:                            |    Component:  MSN    
  Version:  2.2.1                     |   Resolution:  invalid
 Keywords:  gnutls tls handshake msn  |  
--------------------------------------+-------------------------------------

Comment(by freezy):

 Replying to [comment:7 gagern]:
 > Get the same debug messages (unexpected length from omega...) on Gentoo
 with gnutls-2.6.3 and pidgin-2.5.4. In the Pidgin UI, it keeps connecting
 to MSN forever. Disabling and re-enabling the MSN account has some chance
 of resolving the issue, though I couldn't reproduce that aspect yet with
 the debug messages enabled.

 I am having the same issue as '''gagern''' on Debian with gnutls-2.4.2 and
 pidgin-2.5.4. Disabling and re-enabling the MSN account sometimes results
 in a successful connection, it seems somewhat random.


 The failure:
 {{{
 (20:56:00) proxy: Attempting connection to 65.54.170.19
 (20:56:00) proxy: Connecting to omega.contacts.msn.com:443.
 (20:56:00) gnutls: Starting handshake with omega.contacts.msn.com
 (20:56:00) gnutls: Handshake failed. Error A TLS packet with unexpected
 length was received.
 }}}

 Account disabled, re-enabled:

 {{{
 ...
 (20:55:58) soap: Received secure request.
 (20:55:58) soap: Received secure request.
 (20:56:52) soap: read 14115 bytes
 (20:56:52) gnutls: receive failed: A TLS packet with unexpected length was
 received.
 (20:56:52) soap: read: Input/output error
 (20:56:52) soap: Received secure request.
 ...
 }}}

 (continues as if nothing went wrong)

 {{{
 ...
 (20:56:53) proxy: Attempting connection to 65.54.170.30
 (20:56:53) proxy: Connecting to omega.contacts.msn.com:443.
 (20:56:53) gnutls: Starting handshake with omega.contacts.msn.com
 (20:56:53) gnutls: Handshake complete
 (20:56:53) gnutls/x509: Key print:
 de:27:b1:dd:f7:16:d6:4e:46:4d:59:ca:02:ef:3a:9a:38:bc:a1:e0
 (20:56:53) gnutls/x509: Key print:
 7e:8a:c2:9c:5a:32:8c:c2:71:a2:d9:4f:75:70:f7:a9:1b:f6:94:05
 (20:56:53) gnutls/x509: Key print:
 3d:29:1d:b8:ee:22:be:e1:33:70:06:f2:ef:c6:f9:db:dd:03:bb:25
 (20:56:53) gnutls: Peer provided 3 certs
 ...
 }}}

 Connection works as expected.

 Note that the failure occurred when omega.contacts.msn.com resolved to
 65.54.170.19, but not when it resolved to 65.54.170.30.

 Possible temporary solution: append 'omega.contacts.msn.com 65.54.170.30'
 to the system hosts file, assuming 65.54.170.19 is the problem. It
 explains why disabling/re-enabling works with some chance. The domain
 seems to be assigned to several IPs, some of which may not be handling
 handshakes correctly.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3456#comment:8>
Pidgin <http://pidgin.im>
Pidgin