netdev - Re: [net-next] tcp: add TCP_INFO status for failed client TFO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 21 Oct 2019 12:02:07 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     William Dauchy <wdauchy@...il.com>, Jason Baron <jbaron@...mai.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        NETDEV <netdev@...r.kernel.org>,
        Neal Cardwell <ncardwell@...gle.com>,
        Christoph Paasch <cpaasch@...le.com>
Subject: Re: [net-next] tcp: add TCP_INFO status for failed client TFO

On 10/21/19 11:49 AM, William Dauchy wrote:

> I'm curious what would be the arguments compared to creating a new
> getsockopt() to fetch this data?

Reporting tsval/tsecr values were not well defined and seemed quite experimental to me.

TCP fastopen would use 2 unused bits, not real extra cost here.

This is persistent information after the connect(), while your tsval/tsecr report
seems quite dynamic stuff can be stale as soon as the info is fetched from the kernel.