netdev - Re: [PATCH v7 bpf-next 0/3] Introduce CAP

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] [day] [month] [year] [list]

Message-ID: <6f56ba3e-144f-29be-c35d-0506fe16830f@iogearbox.net>
Date:   Fri, 15 May 2020 17:55:20 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>,
        davem@...emloft.net
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org, kernel-team@...com,
        linux-security-module@...r.kernel.org, acme@...hat.com,
        jamorris@...ux.microsoft.com, jannh@...gle.com, kpsingh@...gle.com
Subject: Re: [PATCH v7 bpf-next 0/3] Introduce CAP_BPF

On 5/14/20 1:03 AM, Alexei Starovoitov wrote:
> From: Alexei Starovoitov <ast@...nel.org>
> 
> v6->v7:
> - permit SK_REUSEPORT program type under CAP_BPF as suggested by Marek Majkowski.
>    It's equivalent to SOCKET_FILTER which is unpriv.

Applied, thanks! I do like the env->{allow_ptr_leaks,bypass_spec_v1,bypass_spec_v4,
bpf_capable} split much better, so there's more clarity which belongs to which.
Potentially this can be even made more fine-grained at some point.