linux-kernel - Re: [PATCH v2 02/10] userns: Add per user namespace sysctls.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160725.195836.1881375122073635224.davem@davemloft.net>
Date:	Mon, 25 Jul 2016 19:58:36 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	containers@...ts.linux-foundation.org, keescook@...omium.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	luto@...capital.net, seth.forshee@...onical.com, kernel@...p.com,
	linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	jann@...jh.net
Subject: Re: [PATCH v2 02/10] userns: Add per user namespace sysctls.

From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Mon, 25 Jul 2016 19:44:50 -0500

> User namespaces have enabled unprivileged users access to a lot more
> data structures and so to catch programs that go crazy we need a lot
> more limits.  I believe some of those limits make sense per namespace.
> As it is easy in some cases to say any more than Y number of those
> per namespace is excessive.   For example a limit of 1,000,000 ipv4
> routes per network namespaces is a sanity check as there are
> currently 621,649 ipv4 prefixes advertized in bgp.

When we give a new namespace to unprivileged users, we honestly should
make the sysctl settings we give to them become "limits".  They can
further constrain the sysctl settings but may not raise them.