netdev - Re: [PATCH bpf-next 1/2] libbpf: stop enforcing kern

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: <fb67f98a-08b4-3184-22f8-7d3fb91c9515@fb.com>
Date:   Fri, 4 Oct 2019 14:36:04 +0000
From:   Alexei Starovoitov <ast@...com>
To:     Andrii Nakryiko <andrii.nakryiko@...il.com>,
        John Fastabend <john.fastabend@...il.com>
CC:     Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH bpf-next 1/2] libbpf: stop enforcing kern_version,
 populate it for users

On 10/4/19 7:32 AM, Andrii Nakryiko wrote:
>> If we are not going to validate the section should we also skip collect'ing it?
> Well, if user supplied version, we will parse and use it to override
> out prepopulated one, so in that sense we do have validation.
> 
> But I think it's fine just to drop it altogether. Will do in v3.
> 

what about older kernel that still enforce it?
May be populate it in bpf_attr while loading, but
don't check it in elf from libbpf?