netdev - Re: [PATCH bpf-next v5 4/9] bpf: Implement cgroup sockaddr hooks for unix sockets

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: <CADKFtnTk9mFvvm2hvb4ynHAykDw+dxtZTfDEwvoke3kCr576aw@mail.gmail.com>
Date: Tue, 26 Sep 2023 13:20:55 -0700
From: Jordan Rife <jrife@...gle.com>
To: Daan De Meyer <daan.j.demeyer@...il.com>
Cc: bpf@...r.kernel.org, kernel-team@...a.com, martin.lau@...ux.dev, 
	netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next v5 4/9] bpf: Implement cgroup sockaddr hooks for
 unix sockets

> That would be great! I think it makes sense to apply the same concept to unix
> sockets so insulating changes to the msg_namelen seems like the way to go.

Just sent a new version of my patch series with this change, so we'll see how
it goes.

> This is not yet allowed. We only allow changing the unix sockaddr length at the
> moment. Maybe in the future we'd want to allow changing INET6 addr lengths
> as well but currently we don't allow this.

Ack. Just curious, as I don't think it would be good to, e.g., have a connect4
hook modifying the address length for an IPv4 address.