confirmation that debian #480041 is a gnutls problem, and steps to reproduce

[Daniel Kahn Gillmor]

On Fri 2008-11-21 13:54:37 -0500, Nikos Mavrogiannopoulos wrote:

> Could you first send me a capture to be used with wireshark so i can
> check precisely what is happening there (gnutls-cli) and rule out any
> gnutls issue?

Attached is a pcap file, and the test key and certificate used by the
server during the communication.  The client had no certificate.

wireshark tells me that the TCP checksums of most packets in the
packet capture are wrong; i don't know why that is, nor do i think
it's particularly relevant, given that this was all done across the
loopback interface.

This packet capture was done with gnutls-cli 2.6.2-1 and with
libgnutls26 from the same version.

Hope this is helpful,

        --dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 480041.pcap
Type: application/cap
Size: 4276 bytes
Desc: packet capture
URL: </pipermail/attachments/20081121/d8b1cf6e/attachment.pcap>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: key.pem
URL: </pipermail/attachments/20081121/d8b1cf6e/attachment.asc>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cert.pem
URL: </pipermail/attachments/20081121/d8b1cf6e/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 826 bytes
Desc: not available
URL: </pipermail/attachments/20081121/d8b1cf6e/attachment.pgp>