[gnutls-devel] Problem with proxied connections on 3.5.3

Nikos Mavrogiannopoulos nmav at gnutls.org
Tue Sep 20 08:56:19 CEST 2016


On Mon, 2016-09-19 at 18:53 +0200, Andreas Metzler wrote:
> On 2016-09-17 Nikos Mavrogiannopoulos <n.mavrogiannopoulos at gmail.com>
> wrote:
> > 
> > On Sat, 2016-09-17 at 12:48 +0200, Andreas Metzler wrote:
> > > 
> > > Could you perhaps provide Marcelo with step-by-step instructions
> > > on how
> > > to generate the session capture?
> > 
> > I'd run wireshark -i eth0 (replace eth0 with the ethernet interface
> [...]
> 
> Thanks. Marcelo has uploaded the capture files:
> > This link has two files:
> > 
> > pcap_gnutls.pcapng (Fail, libgnutls30:amd64  3.5.4-2)
> > pcap_gnutls_v352.pcapng (Working version, libgnutls30:amd64  3.5.2-
> > 3)
> > https://drive.google.com/drive/folders/0B3_AQUiHn1qMcEVjdVpNeHBJUHc

I do not see anything wrong in the capture. I even created a small
program to replay the connection locally (I have a debian installation
on x86_64 with the same packages available), and the connection
continued past the failure point on that system.

I'm searching in the dark here, but the following info could help:
1. run gnutls-cli www.server-that-fails -d 9
2. run valgrind gnutls-cli www.server-that-fails
3. compile the attached program as "gcc -O2 -g sim.c -lgmp -lhogweed &&
./a.out", and also run valgrind ./a.out

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sim.c
Type: text/x-csrc
Size: 1459 bytes
Desc: not available
URL: </pipermail/attachments/20160920/6b56fab5/attachment-0001.c>


More information about the Gnutls-devel mailing list