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  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]
Date:   Sat, 9 May 2020 01:41:02 +0200
From:   Daniel Borkmann <>
To:     Stanislav Fomichev <>,,
Cc:,, Andrey Ignatov <>,
        Martin KaFai Lau <>
Subject: Re: [PATCH bpf-next v5 0/4] bpf: allow any port in bpf_bind helper

On 5/8/20 7:46 PM, Stanislav Fomichev wrote:
> We want to have a tighter control on what ports we bind to in
> the BPF_CGROUP_INET{4,6}_CONNECT hooks even if it means
> connect() becomes slightly more expensive.
> The series goes like this:
> 1. selftests: move existing helpers that make it easy to create
>     listener threads into common test_progs part
> 2. selftests: move some common functionality into network_helpers
> 3. do small refactoring of __inet{,6}_bind() flags to make it easy
>     to extend them with the additional flags
> 4. remove the restriction on port being zero in bpf_bind() helper;
>     add new bind flag to prevent POST_BIND hook from being called
> Acked-by: Andrey Ignatov <>
> Acked-by: Martin KaFai Lau <>
> Stanislav Fomichev (4):
>    selftests/bpf: generalize helpers to control background listener
>    selftests/bpf: move existing common networking parts into
>      network_helpers
>    net: refactor arguments of inet{,6}_bind
>    bpf: allow any port in bpf_bind helper

Applied, thanks!

Powered by blists - more mailing lists