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: <0d1a7bc4-2e9c-73ba-11fb-f233e790b3a6@gmail.com>
Date:   Fri, 25 Nov 2016 21:43:31 +0100
From:   "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To:     "Serge E. Hallyn" <serge@...lyn.com>
Cc:     mtk.manpages@...il.com,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        Seth Forshee <seth.forshee@...onical.com>,
        lkml <linux-kernel@...r.kernel.org>, linux-api@...r.kernel.org
Subject: Re: [PATCH RFC] user-namespaced file capabilities - now with even
 more magic

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.manpages@...il.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 about user namespaces
>>> right now.  
>>
>> True. There's really just this:
>>
>>    Interaction with user namespaces
>>        For a discussion of  the  interaction  of  capabilities  and  user
>>        namespaces, see user_namespaces(7).
>>
>>> I'll come up with a patch for both I think.  Do you have a
>>> deadline for a new release coming up?
>>
>> No deadlines as such. The last couple of years, as a sort of 
>> experiment, I've fallen into the same release cycle as the kernel
>> (typically making a release in the week or so after the kernel release),
>> and I am even using a similar numbering scheme. Ideally, the man-pages
>> patch would go into the release that corresponds to the kernel release
>> that makes the change.
> 
> Cool - I'll write something up in the next few weeks.

Obviously, the sooner you write it, the sooner others may read--and
perhaps test--it.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ