netdev - Re: Question about seccomp / bpf

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:   Thu, 9 May 2019 16:49:19 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Alexei Starovoitov <ast@...com>,
        netdev <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
        Andy Lutomirski <luto@...capital.net>,
        Jann Horn <jannh@...gle.com>, Will Drewry <wad@...omium.org>
Subject: Re: Question about seccomp / bpf

On Thu, May 9, 2019 at 4:30 PM Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
> I'm not sure how that can work. seccomp's prctl accepts a list of insns.
> There is no handle.
> kernel can keep a hashtable of all progs ever loaded and do a search
> in it before loading another one, but that's an ugly hack.
> Another alternative is to attach seccomp prog to parent task
> instead of N childrens.

seccomp's filter is already shared by all the children of whatever
process got the filter attached.

-- 
Kees Cook