Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 9 Nov 2017 22:46:46 -0600
From: "Serge E. Hallyn" <>
To: "Eric W. Biederman" <>
Cc: Mahesh Bandewar (महेश बंडेवार) <>,
	"Serge E. Hallyn" <>,
	Christian Brauner <>,
	Boris Lukashev <>,
	Daniel Micay <>,
	Mahesh Bandewar <>,
	LKML <>,
	Netdev <>,
	Kernel-hardening <>,
	Linux API <>,
	Kees Cook <>,
	Eric Dumazet <>,
	David Miller <>
Subject: Re: Re: [PATCH resend 2/2] userns: control
 capabilities of some user namespaces

Quoting Eric W. Biederman (
> single sandbox.  I am not at all certain that the capabilities is the
> proper place to limit code reachability.

Right, I keep having this gut feeling that there is another way we
should be doing that.  Maybe based on ksplice or perf, or maybe more
based on subsystems.  And I hope someone pursues that.  But I can't put
my finger on it, and meanwhile the capability checks obviously *are* in
fact gates...


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.