Re: Emacs hangs with concurrent TLS connections

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> Have you looked at a verbose log with gnutls-log-level set high?

Good idea.

It starts off normal with all the tls chatter, and then it ends up
here... 

gnutls.c: [9] INT: CLIENT WRITE KEY [16]: 6cecebb7aa1e56ee74f24771b39f996a
gnutls.c: [9] INT: SERVER WRITE KEY [16]: 70c92720b41a6e281485e907d8a439c9
gnutls.c: [3] HSK[0x1848300]: Cipher Suite: RSA_ARCFOUR_SHA1
gnutls.c: [3] HSK[0x1848300]: Initializing internal [write] cipher sessions
gnutls.c: [6] BUF[HSK]: Peeked 0 bytes of Data
gnutls.c: [6] BUF[HSK]: Emptied buffer
gnutls.c: [3] HSK[0x1848300]: FINISHED was send [16 bytes]
gnutls.c: [6] BUF[HSK]: Peeked 0 bytes of Data
gnutls.c: [6] BUF[HSK]: Emptied buffer
gnutls.c: [4] REC[0x1848300]: Sending Packet[0] Handshake(22) with length: 16
gnutls.c: [7] WRITE: Will write 41 bytes to 0x8.
gnutls.c: [7] WRITE: wrote 41 bytes to 0x8. Left 0 bytes. Total 41 bytes.
gnutls.c: [7] 0000 - 16 03 01 00 24 50 ca 9f d8 2c d4 34 33 15 cb 33 
gnutls.c: [7] 0001 - d7 8a de 9c ab 5c 72 0c 5b b2 4b 5b 74 ce d1 47 
gnutls.c: [7] 0002 - 1b f9 db 44 d1 57 9d 9c 21 
gnutls.c: [4] REC[0x1848300]: Sent Packet[1] Handshake(22) with length: 41
gnutls.c: [7] READ: -1 returned from 0x8, errno=11 gerrno=0
gnutls.c: [2] ASSERT: gnutls_buffers.c:322
gnutls.c: [2] ASSERT: gnutls_handshake.c:2525
gnutls.c: [7] READ: Got 5 bytes from 0x9
gnutls.c: [7] READ: read 5 bytes from 0x9
gnutls.c: [7] 0000 - 48 54 54 50 2f 
gnutls.c: [7] RB: Have 0 bytes into buffer. Adding 5 bytes.
gnutls.c: [7] RB: Requested 5 bytes
gnutls.c: [2] ASSERT: gnutls_record.c:507

I think everything up to here is normal.  And then things go wonky:

gnutls.c: [4] REC[0x1841540]: Expected Packet[0] Handshake(22) with length: 1
gnutls.c: [4] REC[0x1841540]: Received Packet[0] Unknown Packet(72) with length: 20527
gnutls.c: [4] REC[0x1841540]: FATAL ERROR: Received packet with length: 20527
gnutls.c: [2] ASSERT: gnutls_record.c:960
gnutls.c: [2] ASSERT: gnutls_buffers.c:1032
gnutls.c: [2] ASSERT: gnutls_handshake.c:1045
gnutls.c: [2] ASSERT: gnutls_handshake.c:2364
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer
gnutls.c: [2] ASSERT: gnutls_record.c:879
gnutls.c: [2] ASSERT: gnutls_buffers.c:1032
gnutls.c: [2] ASSERT: gnutls_handshake.c:1045
gnutls.c: [2] ASSERT: gnutls_handshake.c:2364
gnutls.c: [6] BUF[HSK]: Cleared Data from buffer
gnutls.c: [2] ASSERT: gnutls_record.c:879
gnutls.c: [2] ASSERT: gnutls_buffers.c:1032
gnutls.c: [2] ASSERT: gnutls_handshake.c:1045
gnutls.c: [2] ASSERT: gnutls_handshake.c:2364

and here it just loops forever.

Is the wrong socket being asked to handle the TLS data or something?
Hm...  I don't really know how to proceed to debug this, but it's 100%
reproducible for me, so if you have any suggestions, I can test it out
easily enough.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen