netdev - Re: [PATCH bpf-next v5 1/2] bpf: allow rewriting to ports under ip_unprivileged_port

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]

Date:   Thu, 28 Jan 2021 02:30:11 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Stanislav Fomichev <sdf@...gle.com>
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org, ast@...nel.org,
        daniel@...earbox.net, rdna@...com, kafai@...com
Subject: Re: [PATCH bpf-next v5 1/2] bpf: allow rewriting to ports under
 ip_unprivileged_port_start

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Wed, 27 Jan 2021 11:31:39 -0800 you wrote:
> At the moment, BPF_CGROUP_INET{4,6}_BIND hooks can rewrite user_port
> to the privileged ones (< ip_unprivileged_port_start), but it will
> be rejected later on in the __inet_bind or __inet6_bind.
> 
> Let's add another return value to indicate that CAP_NET_BIND_SERVICE
> check should be ignored. Use the same idea as we currently use
> in cgroup/egress where bit #1 indicates CN. Instead, for
> cgroup/bind{4,6}, bit #1 indicates that CAP_NET_BIND_SERVICE should
> be bypassed.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/2] bpf: allow rewriting to ports under ip_unprivileged_port_start
    https://git.kernel.org/bpf/bpf-next/c/772412176fb9
  - [bpf-next,v5,2/2] selftests/bpf: verify that rebinding to port < 1024 from BPF works
    https://git.kernel.org/bpf/bpf-next/c/8259fdeb3032

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html