All,
If you want to download a WorkInProgress version of Wireshark that supports
TLS1.3 (latest version of draft -18 only!). Please go to:
https://www.wireshark.org/download/automated/
THIS IS NOT THE PRODUCTION VERSION OF WIRESHARK!!!
We owe HUGE thanks to Peter Wu & Alexis La Goutte (core
Hi all,
This is indeed work in progress, the current state can be tracked at:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12779
Note for TLS implementers: Wireshark supports decryption when provided
with the master secret (TLS 1.2 and before), but with TLS 1.3 there are
more secrets. The
On 26 January 2017 at 16:31, Peter Wu wrote:
> Hi all,
>
> This is indeed work in progress, the current state can be tracked at:
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12779
>
> Note for TLS implementers: Wireshark supports decryption when provided
> with the master secret (TLS 1.2
I submitted a PR to address some editorial issues:
https://github.com/tlswg/draft-ietf-tls-iana-registry-updates/pull/5
I also created an issue/PR that adds a “recommended" column for exporters; its
another registry that could use it. I followed the same model as the CS
registry, namely put a Y
> On Jan 18, 2017, at 17:49, David Benjamin wrote:
>
> Do people agree with this plan?
Looks like we got general agreement this is a good approach to follow.
spt
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
