The Test Sample for the (Imaginary or Not) Bug

(No. 0)  No. 1  No. 2  No. 3 

Following the email correspondence previous linked to in previous page, I was suggested by a Wireshark developer to prepare "a smaller capture that can reproduce the issue which does not contain sensitive passwords".

This is the page with such a capture.

---

The uncenz obtained data (dumpcap to get the trace, FFmpeg to get the screencast):

dump_170317_0928_g0n.pcap
pg2/dump_170317_0928_g0n_SSLKEYLOGFILE.txt

---

The files necessary for this study are listed in:

ls-1-2

dump_170317_0928_g0n.pcap
Screen_170317_0928_g0n.webm
pg2/dump_170317_0928_g0n_SSLKEYLOGFILE.txt

and verify to: ls-1-2.sum signed by: ls-1-2.sum.asc

How I deal with the trace is:

$ mkdir tStreams/
$ cp -aiv dump_170317_0928_g0n* tStreams/
$ cd tStreams/
$ tshark-streams.sh -r dump_170317_0928_g0n.pcap \
	-k dump_170317_0928_g0n_SSLKEYLOGFILE.txt 
$ cd ../
$ tshark-hosts-conv.sh -r dump_170317_0928_g0n.pcap \
	-k dump_170317_0928_g0n_SSLKEYLOGFILE.txt 

And that got me these files (pls. notice that the list may change, or just a new one added, don't know yet, after I receive feedback on Wireshark ML):

ls-1pg2

pg2/dump_170317_0928_g0n.conv-ip
pg2/dump_170317_0928_g0n-frame-http-request-full_uri.txt
pg2/dump_170317_0928_g0n.hosts
pg2/dump_170317_0928_g0n.POST
pg2/tshark-hosts-conv_170317_194214.log

which verify to: ls-1pg2.sum signed by: ls-1pg2.sum.asc

You might find dump_dLo.sh script from my uncenz program more useful then downloading each file separately.

Also it might be helpful to you to see how the files are obtained, by perusing other of my (primitive) programs:

tshark-streams

tshark-hosts-conv