public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Topi Miettinen <toiwoton@gmail.com>,
	linux-man@vger.kernel.org, alx.manpages@gmail.com
Cc: mtk.manpages@gmail.com, selinux@vger.kernel.org
Subject: Re: [patch] mount.2: document SELinux use of MS_NOSUID mount flag
Date: Sun, 20 Jun 2021 15:54:42 +1200	[thread overview]
Message-ID: <e1f0ced0-7980-0d09-7fbd-636eee67b7ad@gmail.com> (raw)
In-Reply-To: <20210612085109.20363-1-toiwoton@gmail.com>

Helo Topi,

On 6/12/21 8:51 PM, Topi Miettinen wrote:
> Using mount flag `MS_NOSUID` also affects SELinux domain transitions but
> this has not been documented well.
> 
> Signed-off-by: Topi Miettinen <toiwoton@gmail.com>

Thanks. Patch applied.

Cheers,

Michael

> ---
>  man2/mount.2 | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/mount.2 b/man2/mount.2
> index d8521880b..d7d5b2ad4 100644
> --- a/man2/mount.2
> +++ b/man2/mount.2
> @@ -220,7 +220,9 @@ Do not allow programs to be executed from this filesystem.
>  .TP
>  .B MS_NOSUID
>  Do not honor set-user-ID and set-group-ID bits or file capabilities
> -when executing programs from this filesystem.
> +when executing programs from this filesystem. In addition, SELinux domain
> +transitions require permission nosuid_transition, which in turn needs
> +also policy capability nnp_nosuid_transition.
>  .\" (This is a security feature to prevent users executing set-user-ID and
>  .\" set-group-ID programs from removable disk devices.)
>  .TP
> 


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

      reply	other threads:[~2021-06-20  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  8:51 [patch] mount.2: document SELinux use of MS_NOSUID mount flag Topi Miettinen
2021-06-20  3:54 ` 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=e1f0ced0-7980-0d09-7fbd-636eee67b7ad@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=selinux@vger.kernel.org \
    --cc=toiwoton@gmail.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: 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