From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Eric Hopper <hopper@omnifarious.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: A problem with prctl(2) and proc(5)
Date: Tue, 21 Apr 2020 13:13:15 +0200 [thread overview]
Message-ID: <CAKgNAkhqHnZUuGCMHCDO+QMAjWEAosuAzZxzqJKstbUN0_6=Tg@mail.gmail.com> (raw)
In-Reply-To: <CAJWcbJEr0DxmJch2K-CjidF6oQ+wBn43zBXEBH5XZmDkgT=5kg@mail.gmail.com>
Hello Eric,
On Tue, 24 Oct 2017 at 00:47, Eric Hopper <hopper@omnifarious.org> wrote:
>
> Also... execve(2) should make a passing mention of the DUMPABLE flag
> and point at the prctl documentation where it talks about set-user-ID
> processes. That would've greatly shortened my search for the answer I
> needed.
I added some sentences to the execve(2) page, so that tehre is now a
piece that reads:
* The process's "dumpable" attribute is set to the value 1,
unless a set-user-ID program, a set-group-ID program, or a pro‐
gram with capabilities is being executed, in which case the
dumpable flag may instead be reset to the value in
/proc/sys/fs/suid_dumpable, in the circumstances described
under PR_SET_DUMPABLE in prctl(2). Note that changes to the
"dumpable" attribute may cause ownership of files in the
process's /proc/[pid] directory to change to root:root, as
described in proc(5).
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-21 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 22:26 A problem with prctl(2) and proc(5) Eric Hopper
[not found] ` <CAJWcbJEJDZS34g8v3dG-RAe=W0T-9ti_LUQ=GM9LJiEcetVphA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-23 22:47 ` Eric Hopper
2020-04-21 11:13 ` Michael Kerrisk (man-pages) [this message]
2020-04-21 12:29 ` 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='CAKgNAkhqHnZUuGCMHCDO+QMAjWEAosuAzZxzqJKstbUN0_6=Tg@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=hopper@omnifarious.org \
--cc=linux-man@vger.kernel.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).