linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jann Horn <jann-XZ1E9jl8jIdeoWH0uzbU5w@public.gmane.org>,
	Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@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>,
	Casey Schaufler <casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org>,
	James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
Subject: Re: Review of ptrace Yama ptrace_scope description
Date: Wed, 29 Jun 2016 06:49:47 +0200	[thread overview]
Message-ID: <0a832f69-71fc-0b3e-bdc6-4c17f5ceadf6@gmail.com> (raw)
In-Reply-To: <20160628205007.GA1419-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>

Hi Jann,
...

>> So I've made that section of text:
>>
>>        A  process  that  has the CAP_SYS_PTRACE capability can update the
>>        /proc/sys/kernel/yama/ptrace_scope file with one of the  following
>>        values:
>>
>>        0 ("classic ptrace permissions")
>>               No  additional  restrictions  on  operations  that  perform
>>               PTRACE_MODE_ATTACH checks (beyond those imposed by the com‐
>>               moncap and other LSMs).
>>
>>               The use of PTRACE_TRACEME is unchanged.
>>
>>        1 ("restricted ptrace") [default value]
>>               When    performing    an    operation   that   requires   a
>>               PTRACE_MODE_ATTACH check, the calling process  must  either
>>               have the CAP_SYS_PTRACE capability in the user namespace of
>>               the target process or it  have  a  predefined  relationship
>>               with  the target process.
>
> Nit: The grammar in this sentence seems wrong to me.
> s/or it have/or it must have/?

Yep, thanks for catching that. Fixed now.

Cheers,

Michael


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

  parent reply	other threads:[~2016-06-29  4:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25  7:30 Review of ptrace Yama ptrace_scope description Michael Kerrisk (man-pages)
     [not found] ` <a80772d7-f52a-0943-de24-a0cf8d6b2f7c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-25 14:30   ` Jann Horn
2016-06-28  6:11     ` Michael Kerrisk (man-pages)
     [not found]       ` <0017835d-c672-02fe-dab8-d1b11c100c24-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-28 20:50         ` Jann Horn
     [not found]           ` <20160628205007.GA1419-J1fxOzX/cBvk1uMJSBkQmQ@public.gmane.org>
2016-06-29  4:49             ` Michael Kerrisk (man-pages) [this message]
2016-06-28 20:55       ` Kees Cook
2016-06-29  5:05         ` 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=0a832f69-71fc-0b3e-bdc6-4c17f5ceadf6@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org \
    --cc=jann-XZ1E9jl8jIdeoWH0uzbU5w@public.gmane.org \
    --cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
    --cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).