netdev - Re: [PATCH net-next v7 5/5] selinux: bpf: Add addtional check for bpf object file receive

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: <alpine.LFD.2.20.1710201228150.11454@t440.gateway.2wire.net>
Date:   Fri, 20 Oct 2017 12:28:50 +1100 (AEDT)
From:   James Morris <james.l.morris@...cle.com>
To:     Chenbo Feng <chenbofeng.kernel@...il.com>
cc:     netdev@...r.kernel.org, SELinux <Selinux@...ho.nsa.gov>,
        linux-security-module@...r.kernel.org,
        Jeffrey Vander Stoep <jeffv@...gle.com>,
        Alexei Starovoitov <alexei.starovoitov@...il.com>,
        lorenzo@...gle.com, Daniel Borkmann <daniel@...earbox.net>,
        Stephen Smalley <sds@...ho.nsa.gov>,
        Paul Moore <paul@...l-moore.com>,
        Chenbo Feng <fengc@...gle.com>
Subject: Re: [PATCH net-next v7 5/5] selinux: bpf: Add addtional check for
 bpf object file receive

On Wed, 18 Oct 2017, Chenbo Feng wrote:

> From: Chenbo Feng <fengc@...gle.com>
> 
> Introduce a bpf object related check when sending and receiving files
> through unix domain socket as well as binder. It checks if the receiving
> process have privilege to read/write the bpf map or use the bpf program.
> This check is necessary because the bpf maps and programs are using a
> anonymous inode as their shared inode so the normal way of checking the
> files and sockets when passing between processes cannot work properly on
> eBPF object. This check only works when the BPF_SYSCALL is configured.
> 
> Signed-off-by: Chenbo Feng <fengc@...gle.com>
> Acked-by: Stephen Smalley <sds@...ho.nsa.gov>



Reviewed-by: James Morris <james.l.morris@...cle.com>


-- 
James Morris
<james.l.morris@...cle.com>