netdev - Re: [PATCH net-next 0/2] net: core: Two Helper function about socket information

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]

Message-ID: <CAKD1Yr3REse_WBB0K3YpGsKKyFYDs6Y6Bpmhv4eE+C4c5d29+A@mail.gmail.com>
Date:   Sat, 4 Feb 2017 01:19:28 +0900
From:   Lorenzo Colitti <lorenzo@...gle.com>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Chenbo Feng <chenbofeng.kernel@...il.com>,
        "David S . Miller" <davem@...emloft.net>,
        Alexei Starovoitov <ast@...com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next 0/2] net: core: Two Helper function about socket information

On Fri, Feb 3, 2017 at 9:13 AM, Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
> I think sk_uid is self explanatory, but cookie is less so.
> Please explain how you plan to use it.

The cookie is the only way to uniquely identify a given socket on the
system (the 5-tuple is not sufficient in the presence of SO_REUSEPORT,
for example). One goal for this infrastructure is to perform
per-socket accounting (ultimately replace the out-of-tree xt_qtaguid
code that is used for per-UID, per-socket-tag accounting on Android).
The socket cookie would be a natural key to use in a BPF map where the
values are socket accounting information.