netdev - Re: [PATCH bpf-next 11/15] bpftool: add skeleton codegen command

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: <76684eef-072c-70bb-ed4e-9d23a60eb917@fb.com>
Date:   Tue, 17 Dec 2019 15:45:45 +0000
From:   Alexei Starovoitov <ast@...com>
To:     Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>
CC:     Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH bpf-next 11/15] bpftool: add skeleton codegen command

On 12/17/19 5:59 AM, Daniel Borkmann wrote:
> Given this is mere output of the program and not derivative work of bpftool
> itself, as in bpftool copying chunks of its own code into the generated 
> one,
> this should not need any restriction, but then you'd still need linking
> against libbpf itself to make everything work.

btw generating stuff is the same as compilation. The license of the
tool that is doing it has no bearing on the generated output.
Linking with libbpf is different though, since it's a dependency of the 
output. Hence matching it to libbpf's license is the best.