Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 23 Nov 2011 08:41:56 -0600
From: Serge Hallyn <>
To: Vasiliy Kulikov <>
Cc: Kees Cook <>,,,,
	"Serge E. Hallyn" <>
Subject: Re: [RFC] Make Yama pid_ns aware

Quoting Vasiliy Kulikov (
> > But still, is turning this on and off per-container, and leaving it off
> > on the host, something people will reasonably want to do?
> Probably we need strict rules like ptrace is relaxed iff in both source
> ns and dest ns ptrace is relaxed.

But will people want that?

> > I'm just
> > wondering whether adding the extra data on the pidns is worth it.  It's
> > fine if it is, but I'm having a hard time imagining someone using it
> > like that.
> We have already very big net_namespace with all kind of per-ns stuff.
> Yama's variables don't significantly increase the size of container.

Yes I'm not complaining about the extra host memory usage, just trying
to make sure we don't pollute the pidns struct with something noone

> Actually, what concerns me is not ptrace, but symlink/hardling
> protection.  There is no interaction between namespaces in case of
> containers via symlinks in the basic case.  In case of ptrace I don't
> think the child ns may weaken the parent ns - child ns may not access
> processes of the parent namespace and everything it may ptrace is
> already inside of this ns.

User namespace being respected by VFS will help symlinking.


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.