netdev - Re: New skb extension for use by LSMs (skb "security blob")?

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: <5d524e45-0d80-3a1c-4fd2-7610d2197bf8@schaufler-ca.com>
Date:   Thu, 22 Aug 2019 15:34:44 -0700
From:   Casey Schaufler <casey@...aufler-ca.com>
To:     David Miller <davem@...emloft.net>
Cc:     fw@...len.de, paul@...l-moore.com, netdev@...r.kernel.org,
        linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
        casey@...aufler-ca.com
Subject: Re: New skb extension for use by LSMs (skb "security blob")?

On 8/22/2019 3:28 PM, David Miller wrote:
> From: Casey Schaufler <casey@...aufler-ca.com>
> Date: Thu, 22 Aug 2019 14:59:37 -0700
>
>> Sure, you *can* do that, but it would be insane to do so.
> We look up the neighbour table entries on every single packet we
> transmit from the kernel in the same exact way.
>
> And it was exactly to get rid of a pointer in a data structure.

I very much expect that the lifecycle management issues would
be completely different, but I'll admit to having little understanding
of the details of the neighbour table.