After looking at this, I'd have to say the DTLS decryption test is flawed.
It sets up a key to decifer traffic as HTTP, but it's not really HTTP, it's
just a bunch of ASCII strings. I can change it to any of the valid dissectors
and presuming the DTLS decyption is done correctly (which I
On Thu, Apr 24, 2014 at 4:41 PM, mman...@netscape.net wrote:
After looking at this, I'd have to say the DTLS decryption test is flawed.
It sets up a key to decifer traffic as HTTP, but it's not really HTTP, it's
just a bunch of ASCII strings. I can change it to any of the valid
dissectors
On Thursday 24 April 2014 16:41:02 mman...@netscape.net wrote:
After looking at this, I'd have to say the DTLS decryption test is
flawed. It sets up a key to decifer traffic as HTTP, but it's not really
HTTP, it's just a bunch of ASCII strings. I can change it to any of the
valid dissectors
On Wed, Apr 23, 2014 at 4:20 AM, Evan Huus eapa...@gmail.com wrote:
The DTLS decryption test has been failing for the last few days
because of this. Not sure what the relation is, but...
When try to look the output of DTLS decryption test, it is empty (and
use HTTP filter..)
env $TS_DC_ENV
The DTLS decryption test has been failing for the last few days
because of this. Not sure what the relation is, but...
On Sun, Apr 20, 2014 at 8:40 AM, Wireshark code review
code-review-do-not-re...@wireshark.org wrote:
URL:
