Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 4349] Add support for TLS key logs

Date: Tue, 22 Dec 2009 21:39:00 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4349

--- Comment #4 from Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx> 2009-12-22 22:38:59 MST ---
(In reply to comment #3)
> Created an attachment (id=4087)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4087) [details]
> Capture of a trivial RSA ciphersuite TLS connection.

Thanks.  Are you able to attach a log file for testing too?

> This is a capture of a TLS connection that I used for fuzz testing. I left
> fuzz-test.sh running for 35 minutes (8257 iterations), I don't know what the
> normal length of time is.

That is plenty.  I usually let it run 100 iterations, but the buildbots only do
25 (for example
http://buildbot.wireshark.org/trunk/builders/Ubuntu-7.10-x86-64/builds/343/steps/fuzz-menagerie/logs/stdio)

> I wasn't sure if the preferences would be in effect for fuzz testing, so I
> hardcoded the path to the key log file for the test and verified that the new
> code was getting exercised by strace'ing and checking for the key log file
> being opened.

The preferences are picked up when fuzz testing because tools/fuzz-test.sh runs
tshark with some extra options.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.