All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: Topi Miettinen <toiwoton@gmail.com>, selinux@vger.kernel.org
Cc: Topi Miettinen <toiwoton@gmail.com>
Subject: Re: [PATCH] selinux.8: document how mount flag nosuid affects SELinux
Date: Fri, 18 Jun 2021 16:51:19 +0200	[thread overview]
Message-ID: <87pmwj1b14.fsf@redhat.com> (raw)
In-Reply-To: <20210612090738.22408-1-toiwoton@gmail.com>

Topi Miettinen <toiwoton@gmail.com> writes:

> Using mount flag `nosuid` also affects SELinux domain transitions but
> this has not been documented well.
>
> Signed-off-by: Topi Miettinen <toiwoton@gmail.com>
>

Acked-by: Petr Lautrbach <plautrba@redhat.com>

Merged. Thanks!


> ---
>  libselinux/man/man8/selinux.8 | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/libselinux/man/man8/selinux.8 b/libselinux/man/man8/selinux.8
> index 0ef01460..5842150b 100644
> --- a/libselinux/man/man8/selinux.8
> +++ b/libselinux/man/man8/selinux.8
> @@ -94,6 +94,13 @@ and reboot.
>  also has this capability.  The
>  .BR restorecon / fixfiles
>  commands are also available for relabeling files.
> +
> +Please note that using mount flag
> +.I nosuid
> +also disables SELinux domain transitions, unless permission
> +.I nosuid_transition
> +is used in the policy to allow this, which in turn needs also policy capability
> +.IR nnp_nosuid_transition .
>  .
>  .SH AUTHOR
>  This manual page was written by Dan Walsh <dwalsh@redhat.com>.
> -- 
> 2.30.2


      reply	other threads:[~2021-06-18 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  9:07 [PATCH] selinux.8: document how mount flag nosuid affects SELinux Topi Miettinen
2021-06-18 14:51 ` Petr Lautrbach [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=87pmwj1b14.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --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 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.