From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> To: Casey Schaufler <casey@schaufler-ca.com>, John Stultz <john.stultz@linaro.org> Cc: mtk.manpages@gmail.com, "Serge E. Hallyn" <serge@hallyn.com>, James Morris <jmorris@namei.org>, Kees Cook <keescook@chromium.org>, Andy Lutomirski <luto@amacapital.net>, Jann Horn <jann@thejh.net>, "Eric W. Biederman" <ebiederm@xmission.com>, linux-man <linux-man@vger.kernel.org>, linux-security-module <linux-security-module@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org> Subject: Re: RFC: capabilities(7): notes for kernel developers Date: Fri, 16 Dec 2016 15:55:35 +0100 [thread overview] Message-ID: <e8a6d266-9870-2591-576b-927208683b5d@gmail.com> (raw) In-Reply-To: <7a6b5f38-de8e-d8d4-e6f7-feae3f8d192e@schaufler-ca.com> On 12/16/2016 01:44 AM, Casey Schaufler wrote: > On 12/15/2016 4:31 PM, John Stultz wrote: >> On Thu, Dec 15, 2016 at 12:40 PM, Casey Schaufler >> <casey@schaufler-ca.com> wrote: >>> On 12/15/2016 11:41 AM, Michael Kerrisk (man-pages) wrote: >>>> On 12/15/2016 05:29 PM, Casey Schaufler wrote: >>>>> CAP_WAKE_ALARM could readily be CAP_TIME. >>>> Actually, I don't quite understand what you mean with that sentence. >>>> Could you elaborate? >>> Should have said CAP_SYS_TIME >>> >>> Setting an alarm could be considered a time management function, >>> depending on what it actually does. >> Just a nit here. CAP_WAKE_ALARM is more about the privilege of waking >> a system from suspend, while CAP_SYS_TIME covers the ability to set >> the time. One wouldn't necessarily want to give applications which >> could wake a system up the capability to also set the time. > > Doesn't really matter, except that an ignorant developer > might make the mistake I did and assume that WAKE_ALARM > was somehow related to time management. If you want to use > it as an example don't let my dunderheadedness get in your > way. Actually, I decided it wasn't such a good example anyway. That capability could potentially be generic. (But it probably should better have been named something like 'CAP_WAKE_SYSTEM'.) >> thanks >> -john > > Again, thank you for taking this on. It should be a > big help. You're welcome. And thanks for your help, Casey. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> To: Casey Schaufler <casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org>, John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>, James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>, Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>, Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>, Jann Horn <jann-XZ1E9jl8jIdeoWH0uzbU5w@public.gmane.org>, "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>, linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-security-module <linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: Re: RFC: capabilities(7): notes for kernel developers Date: Fri, 16 Dec 2016 15:55:35 +0100 [thread overview] Message-ID: <e8a6d266-9870-2591-576b-927208683b5d@gmail.com> (raw) In-Reply-To: <7a6b5f38-de8e-d8d4-e6f7-feae3f8d192e-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org> On 12/16/2016 01:44 AM, Casey Schaufler wrote: > On 12/15/2016 4:31 PM, John Stultz wrote: >> On Thu, Dec 15, 2016 at 12:40 PM, Casey Schaufler >> <casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org> wrote: >>> On 12/15/2016 11:41 AM, Michael Kerrisk (man-pages) wrote: >>>> On 12/15/2016 05:29 PM, Casey Schaufler wrote: >>>>> CAP_WAKE_ALARM could readily be CAP_TIME. >>>> Actually, I don't quite understand what you mean with that sentence. >>>> Could you elaborate? >>> Should have said CAP_SYS_TIME >>> >>> Setting an alarm could be considered a time management function, >>> depending on what it actually does. >> Just a nit here. CAP_WAKE_ALARM is more about the privilege of waking >> a system from suspend, while CAP_SYS_TIME covers the ability to set >> the time. One wouldn't necessarily want to give applications which >> could wake a system up the capability to also set the time. > > Doesn't really matter, except that an ignorant developer > might make the mistake I did and assume that WAKE_ALARM > was somehow related to time management. If you want to use > it as an example don't let my dunderheadedness get in your > way. Actually, I decided it wasn't such a good example anyway. That capability could potentially be generic. (But it probably should better have been named something like 'CAP_WAKE_SYSTEM'.) >> thanks >> -john > > Again, thank you for taking this on. It should be a > big help. You're welcome. And thanks for your help, Casey. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-12-16 14:55 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-15 11:40 RFC: capabilities(7): notes for kernel developers Michael Kerrisk (man-pages) 2016-12-15 11:40 ` Michael Kerrisk (man-pages) 2016-12-15 16:29 ` Casey Schaufler 2016-12-15 16:29 ` Casey Schaufler 2016-12-15 19:41 ` Michael Kerrisk (man-pages) 2016-12-15 20:40 ` Casey Schaufler 2016-12-15 20:40 ` Casey Schaufler 2016-12-16 0:31 ` John Stultz 2016-12-16 0:31 ` John Stultz 2016-12-16 0:44 ` Casey Schaufler 2016-12-16 14:55 ` Michael Kerrisk (man-pages) [this message] 2016-12-16 14:55 ` Michael Kerrisk (man-pages) 2016-12-16 20:10 ` Serge E. Hallyn 2016-12-16 20:10 ` Serge E. Hallyn 2016-12-16 20:20 ` John Stultz 2016-12-16 21:05 ` Serge E. Hallyn 2016-12-16 21:16 ` John Stultz 2016-12-16 21:16 ` John Stultz 2016-12-19 20:20 ` Rafael J. Wysocki 2016-12-19 20:20 ` Rafael J. Wysocki 2016-12-17 21:01 ` Michael Kerrisk (man-pages) 2016-12-16 15:04 ` Michael Kerrisk (man-pages) 2016-12-16 15:04 ` Michael Kerrisk (man-pages)
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=e8a6d266-9870-2591-576b-927208683b5d@gmail.com \ --to=mtk.manpages@gmail.com \ --cc=casey@schaufler-ca.com \ --cc=ebiederm@xmission.com \ --cc=jann@thejh.net \ --cc=jmorris@namei.org \ --cc=john.stultz@linaro.org \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-man@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=luto@amacapital.net \ --cc=serge@hallyn.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.