Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-09 Thread Eric W. Biederman
ebied...@xmission.com (Eric W. Biederman) writes: > "Serge E. Hallyn" writes: > >> Quoting Eric W. Biederman (ebied...@xmission.com): >>> "Serge E. Hallyn" writes: >>> >>> > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >>> >> "Serge E. Hallyn" writes: >>> >>> >> Any chan

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-09 Thread Eric W. Biederman
"Serge E. Hallyn" writes: > Quoting Eric W. Biederman (ebied...@xmission.com): >> "Serge E. Hallyn" writes: >> >> > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >> >> "Serge E. Hallyn" writes: >> >> >> Any chance of a singed-off-by? >> > >> > Yes, sorry, Stéphane had poi

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-09 Thread Serge E. Hallyn
Quoting Eric W. Biederman (ebied...@xmission.com): > "Serge E. Hallyn" writes: > > > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: > >> "Serge E. Hallyn" writes: > > >> Any chance of a singed-off-by? > > > > Yes, sorry, Stéphane had pointed out that I'd apparently forgotten

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-09 Thread Eric W. Biederman
"Serge E. Hallyn" writes: > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >> "Serge E. Hallyn" writes: >> Any chance of a singed-off-by? > > Yes, sorry, Stéphane had pointed out that I'd apparently forgotten to do > -s. Do you want me to resend the whole shebang, or does >

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-07 Thread Eric W. Biederman
"Serge E. Hallyn" writes: > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >> "Serge E. Hallyn" writes: >> >> > Root in a user ns cannot be trusted to write a traditional >> > security.capability xattr. If it were allowed to do so, then any >> > unprivileged user on the hos

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-07 Thread Serge E. Hallyn
On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: > "Serge E. Hallyn" writes: > > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could map his own uid to root in

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-12-07 Thread Eric W. Biederman
"Serge E. Hallyn" writes: > Root in a user ns cannot be trusted to write a traditional > security.capability xattr. If it were allowed to do so, then any > unprivileged user on the host could map his own uid to root in a > namespace, write the xattr, and execute the file with privilege on the >

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-29 Thread Serge E. Hallyn
Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > On 11/25/2016 06:50 PM, Serge E. Hallyn wrote: > > On Fri, Nov 25, 2016 at 09:33:50AM +0100, Michael Kerrisk (man-pages) wrote: > >> Hi Serge, > >> > >> On 11/24/2016 11:52 PM, Serge E. Hallyn wrote: > >>> Quoting Michael Kerrisk (man-

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-25 Thread Michael Kerrisk (man-pages)
On 11/25/2016 06:50 PM, Serge E. Hallyn wrote: > On Fri, Nov 25, 2016 at 09:33:50AM +0100, Michael Kerrisk (man-pages) wrote: >> Hi Serge, >> >> On 11/24/2016 11:52 PM, Serge E. Hallyn wrote: >>> Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): >> >> [...] >> Could we have a man-p

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-25 Thread Serge E. Hallyn
On Fri, Nov 25, 2016 at 09:33:50AM +0100, Michael Kerrisk (man-pages) wrote: > Hi Serge, > > On 11/24/2016 11:52 PM, Serge E. Hallyn wrote: > > Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > > [...] > > >> Could we have a man-pages patch for this feature? Presumably for > >> us

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-25 Thread Michael Kerrisk (man-pages)
Hi Serge, On 11/24/2016 11:52 PM, Serge E. Hallyn wrote: > Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): [...] >> Could we have a man-pages patch for this feature? Presumably for >> user_namespaces(7) or capabilities(7). > > capabilities.7 doesn't actually mention anything abou

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-24 Thread Serge E. Hallyn
Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com): > Hi Serge, > > On 11/19/2016 04:17 PM, Serge E. Hallyn wrote: > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-24 Thread Michael Kerrisk (man-pages)
Hi Serge, On 11/19/2016 04:17 PM, Serge E. Hallyn wrote: > Root in a user ns cannot be trusted to write a traditional > security.capability xattr. If it were allowed to do so, then any > unprivileged user on the host could map his own uid to root in a > namespace, write the xattr, and execute the

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-23 Thread Eric W. Biederman
"Serge E. Hallyn" writes: > Root in a user ns cannot be trusted to write a traditional > security.capability xattr. If it were allowed to do so, then any > unprivileged user on the host could map his own uid to root in a > namespace, write the xattr, and execute the file with privilege on the >

[PATCH RFC] user-namespaced file capabilities - now with even more magic

2016-11-19 Thread Serge E. Hallyn
Root in a user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any unprivileged user on the host could map his own uid to root in a namespace, write the xattr, and execute the file with privilege on the host. This patch introduces v3 of the