Hi Chris,
I think, it is a good idea and no too complicated to implement !
Cheers
On Mon, Feb 10, 2020 at 8:58 PM Maynard, Chris via Wireshark-dev <
wireshark-dev@wireshark.org> wrote:
> In light of these 3 CVE’s, CVE-2019-11477, 11478 and 11479[3], and the
> apparently effective work-around to
In light of these 3 CVE's, CVE-2019-11477, 11478 and 11479[3], and the
apparently effective work-around to avoid them according to the recent December
2019 Internet Protocol Journal[4] article, "MSS Values of TCP" by Geoff Huston,
should Wireshark add an Expert Info for any TCP MSS value seen of
