Re: [PATCH 0/2] Rename nsproxy.pid_ns and fix a related security bug

2013-08-27 Thread David Miller
From: Andy Lutomirski Date: Thu, 22 Aug 2013 11:39:14 -0700 > Eric fell for my bogus claim that nsproxy->pid_ns was the current' > process's pid ns. This isn't true. > > Let's fix the bug and rename pid_ns so that no one gets this wrong again. > > Signed-off-by: Andy Lutomirski Series applie

Re: [PATCH 0/2] Rename nsproxy.pid_ns and fix a related security bug

2013-08-26 Thread Eric W. Biederman
David Miller writes: > From: Andy Lutomirski > Date: Thu, 22 Aug 2013 11:39:14 -0700 > >> commit 92f28d973cce45ef5823209aab3138eb45d8b349 >> Author: Eric W. Biederman >> Date: Fri Mar 15 01:03:33 2013 -0700 >> >> scm: Require CAP_SYS_ADMIN over the current pidns to spoof

Re: [PATCH 0/2] Rename nsproxy.pid_ns and fix a related security bug

2013-08-26 Thread David Miller
From: Andy Lutomirski Date: Thu, 22 Aug 2013 11:39:14 -0700 > commit 92f28d973cce45ef5823209aab3138eb45d8b349 > Author: Eric W. Biederman > Date: Fri Mar 15 01:03:33 2013 -0700 > > scm: Require CAP_SYS_ADMIN over the current pidns to spoof pids. > > Eric fell for my bogus

[PATCH 0/2] Rename nsproxy.pid_ns and fix a related security bug

2013-08-22 Thread Andy Lutomirski
In: commit 92f28d973cce45ef5823209aab3138eb45d8b349 Author: Eric W. Biederman Date: Fri Mar 15 01:03:33 2013 -0700 scm: Require CAP_SYS_ADMIN over the current pidns to spoof pids. Eric fell for my bogus claim that nsproxy->pid_ns was the current' process's pid ns. This is