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
| ||
|
Message-ID: <CAF2d9jifsKH+67m8QsC9O0_21KiMOPKRU+=M_9xyJ-Y03bMwRw@mail.gmail.com> Date: Wed, 28 Dec 2022 10:40:36 -0800 From: Mahesh Bandewar (महेश बंडेवार) <maheshb@...gle.com> To: Jakub Kicinski <kuba@...nel.org> Cc: Netdev <netdev@...r.kernel.org>, Mahesh Bandewar <mahesh@...dewar.net>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Soheil Hassas Yeganeh <soheil@...gle.com> Subject: Re: [PATCH next] sysctl: expose all net/core sysctls inside netns On Thu, Dec 22, 2022 at 6:12 PM Jakub Kicinski <kuba@...nel.org> wrote: > > On Thu, 22 Dec 2022 11:10:05 -0800 Mahesh Bandewar wrote: > > All were not visible to the non-priv users inside netns. However, > > with 4ecb90090c84 ("sysctl: allow override of /proc/sys/net with > > CAP_NET_ADMIN"), these vars are protected from getting modified. > > A proc with capable(CAP_NET_ADMIN) can change the values so > > not having them visible inside netns is just causing nuisance to > > process that check certain values (e.g. net.core.somaxconn) and > > see different behavior in root-netns vs. other-netns > > SG, but net-next is closed, please repost after New Year. My bad, thanks for the note. Happy holidays and will post it next year.
Powered by blists - more mailing lists