From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Shawn Landden <shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/5] kcmp.2: note about SECURITY_YAMA
Date: Sun, 29 Dec 2013 00:33:12 +1300 [thread overview]
Message-ID: <52BEB6F8.5040302@gmail.com> (raw)
In-Reply-To: <1387586263-9002-1-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
Shawn,
Can you supply more background on this patch.
Looking at security/yama/yama_lsm.c:
[[
#define YAMA_SCOPE_DISABLED 0
#define YAMA_SCOPE_RELATIONAL 1
#define YAMA_SCOPE_CAPABILITY 2
#define YAMA_SCOPE_NO_ATTACH 3
static int ptrace_scope = YAMA_SCOPE_RELATIONAL;
]]
This suggests that your statement that the default value is 2 is incorrect,
but I may be missing something.
Cheers,
Michael
On 12/21/13 13:37, Shawn Landden wrote:
> Signed-off-by: Shawn Landden <shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
> ---
> man2/kcmp.2 | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/man2/kcmp.2 b/man2/kcmp.2
> index 59dd4d1..c910ac2 100644
> --- a/man2/kcmp.2
> +++ b/man2/kcmp.2
> @@ -187,7 +187,12 @@ is invalid.
> Insufficient permission to inspect process resources.
> The
> .B CAP_SYS_PTRACE
> -capability is required to inspect processes that you do not own.
> +capability is required to inspect processes that you do not own. Other
> +limitations on ptrace apply, such as
> +.BR CONFIG_SECURITY_YAMA ,
> +which when /proc/sys/kernel/yama/ptrace_scope is 2 (the default) limits
> +.BR kcmp()
> +to child processes.
> .TP
> .B ESRCH
> Process
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
--
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
prev parent reply other threads:[~2013-12-28 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 0:37 [PATCH 1/5] kcmp.2: note about SECURITY_YAMA Shawn Landden
[not found] ` <1387586263-9002-1-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
2013-12-21 0:37 ` [PATCH 2/5] cmsg: be not --> not be Shawn Landden
[not found] ` <1387586263-9002-2-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
2013-12-28 11:34 ` Michael Kerrisk (man-pages)
2013-12-21 0:37 ` [PATCH 3/5] timerfd_create: add timerfd(2) alias Shawn Landden
[not found] ` <1387586263-9002-3-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
2013-12-28 11:35 ` Michael Kerrisk (man-pages)
2013-12-21 0:37 ` [PATCH 4/5] printf: %m is supported by uclibc and musl, no %n in bionic Shawn Landden
[not found] ` <1387586263-9002-4-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
2016-06-09 8:37 ` Michael Kerrisk (man-pages)
2013-12-21 0:37 ` [PATCH 5/5] FreeBSD and bionic have memmem Shawn Landden
[not found] ` <1387586263-9002-5-git-send-email-shawn-01I/ocv1qBBILuwUvNxBeQ@public.gmane.org>
2016-06-09 8:00 ` Michael Kerrisk (man-pages)
2013-12-28 11:33 ` Michael Kerrisk (man-pages) [this message]
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=52BEB6F8.5040302@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn-01I/ocv1qBBILuwUvNxBeQ@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).