netdev - RE: Bpftool mirror now available

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: <CH2PR21MB14640448106792E7197A042CA35A9@CH2PR21MB1464.namprd21.prod.outlook.com>
Date:   Thu, 20 Jan 2022 14:19:05 +0000
From:   Dave Thaler <dthaler@...rosoft.com>
To:     Quentin Monnet <quentin@...valent.com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>
CC:     Jakub Kicinski <kuba@...nel.org>,
        Andrii Nakryiko <andrii@...nel.org>
Subject: RE: Bpftool mirror now available

Quentin Monnet <quentin@...valent.com> wrote:
> Hi, I have the pleasure to announce the availability of a mirror for bpftool on GitHub, at the following URL:
> [...]
> 3. Another objective was to help other projects build on top of the existing sources for bpftool. I'm thinking in
> particular of eBPF-for-Windows, which has been working on a proof-of-concept port of the tool for Windows [1]. 
> Bpftool's mirror keeps the minimal amount of necessary headers, and stripped most of them from the definitions
> that are not required in our context, which should make it easier to uncouple bpftool from Linux.
> [...]
> Just to make it clear, bpftool's mirror does not change the fact that all bpftool development happens on the
> kernel mailing-lists (in particular, the BPF mailing-list), and that the sources hosted in the kernel repository
> remain the reference for the tool. At this time the GitHub repository is just a mirror, and will not accept pull
> requests on bpftool's sources.

Thanks Quentin, this is a great first step!   I can update the ebpf-for-windows project to use this as a submodule.

Longer term, is the goal to make the mirror be the authoritative reference, or to make the Linux kernel repository
not be Linux-only but accept non-Linux patches to bpftool?

Dave