Linux Manual Pages development
 help / color / mirror / Atom feed
From: Patsy Griffin <patsy@redhat.com>
To: alx+linux-man@kernel.org
Cc: linux-man@vger.kernel.org, codonell@redhat.com,
	fweimer@redhat.com, Patsy Griffin <patsy@redhat.com>,
	Carlos O'Donell <carlos@redhat.com>
Subject: [PATCH] man/man7/credentials.7: Mention potential SELinux impact on credentials
Date: Tue, 17 Nov 2026 11:10:46 -0500	[thread overview]
Message-ID: <20261117161046.2037417-1-patsy@redhat.com> (raw)

An SELinux context may impact traditional credential access control.

Link: <https://bugzilla.redhat.com/show_bug.cgi?id=884625>
Cc: Florian Weimer <fweimer@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>
Signed-off-by: Patsy Griffin <patsy@redhat.com>
---
 man/man7/credentials.7 | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/man/man7/credentials.7 b/man/man7/credentials.7
index b538b1702..21e42ec30 100644
--- a/man/man7/credentials.7
+++ b/man/man7/credentials.7
@@ -335,6 +335,12 @@ is carried through to all of the POSIX threads in a process.
 See
 .BR nptl (7)
 for further details.
+.P
+Credentials may also be impacted by Security-Enhanced Linux (SELinux),
+if enabled.
+See
+.BR selinux (8)
+for further details.
 .SH SEE ALSO
 .BR bash (1),
 .BR csh (1),
@@ -386,4 +392,5 @@ for further details.
 .BR system_data_types (7),
 .BR unix (7),
 .BR user_namespaces (7),
+.BR selinux (8),
 .BR sudo (8)
-- 
2.56.0


             reply	other threads:[~2026-11-18  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 16:10 Patsy Griffin [this message]
2026-11-18  0:13 ` [PATCH] man/man7/credentials.7: Mention potential SELinux impact on credentials Carlos O'Donell
2026-11-18  0:30   ` Alejandro Colomar

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=20261117161046.2037417-1-patsy@redhat.com \
    --to=patsy@redhat.com \
    --cc=alx+linux-man@kernel.org \
    --cc=carlos@redhat.com \
    --cc=codonell@redhat.com \
    --cc=fweimer@redhat.com \
    --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