[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQ+GL6sYCff4eU4WXZYeZSi5BJ5amy6NQjuZk2=OjuM5+g@mail.gmail.com>
Date: Thu, 27 Apr 2017 07:49:29 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Jiri Benc <jbenc@...hat.com>,
Aaron Conole <aconole@...heb.org>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next 4/6] bpf: track if the bpf program was loaded
with SYS_ADMIN capabilities
On Thu, Apr 27, 2017 at 6:17 AM, Hannes Frederic Sowa
<hannes@...essinduktion.org> wrote:
>
> cap_sys_admin influences the verifier a lot in terms which programs are
> accepted and which are not. So during investigations it might be even
> interesting if the bpf program required those special flags or if the
> same program could be loaded just as underprivileged.
there are bunch of other things that influence verifier.
should we add all of them ?
there is prog->aux->user which is more than enough for
debugging.
Powered by blists - more mailing lists