From: "Günther Noack" <gnoack3000@gmail.com>
To: Alejandro Colomar <alx+linux-man@kernel.org>
Cc: "Günther Noack" <gnoack3000@gmail.com>,
linux-man@vger.kernel.org,
"Kuniyuki Iwashima" <kuniyu@google.com>
Subject: [PATCH v3 2/5] man/man7/unix.7: SO_PASSSEC: wfix
Date: Fri, 20 Nov 2026 17:11:59 +0100 [thread overview]
Message-ID: <20261120161202.27163-3-gnoack3000@gmail.com> (raw)
In-Reply-To: <20261120161202.27163-1-gnoack3000@gmail.com>
Use "security context", as in the description of SCM_SECURITY.
Cc: Kuniyuki Iwashima <kuniyu@google.com>
Assisted-by: LLM
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Signed-off-by: Günther Noack <gnoack3000@gmail.com>
---
man/man7/unix.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man7/unix.7 b/man/man7/unix.7
index 3322d915f1bb..532c50b94ec3 100644
--- a/man/man7/unix.7
+++ b/man/man7/unix.7
@@ -312,7 +312,7 @@ .SS Socket options
is an integer boolean flag.
.TP
.B SO_PASSSEC
-Enables receiving of the security label of the peer socket
+Enables receiving of the security context of the peer socket
in an ancillary message of type
.B SCM_SECURITY
(see below).
--
2.56.1
next prev parent reply other threads:[~2026-11-20 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 16:11 [PATCH v3 0/5] unix.7: Socket Options and SCM_* fixes Günther Noack
2026-11-20 16:11 ` [PATCH v3 1/5] man/man7/unix.7: SCM_SECURITY: Generalize to other LSMs, not just SELinux Günther Noack
2026-11-20 16:11 ` Günther Noack [this message]
2026-11-20 16:12 ` [PATCH v3 3/5] man/man7/unix.7: Document SO_PASSPIDFD, SO_PEERPIDFD, and SCM_PIDFD Günther Noack
2026-11-20 16:12 ` [PATCH v3 4/5] man/man7/unix.7: Document SO_PASSRIGHTS Günther Noack
2026-11-20 16:12 ` [PATCH v3 5/5] man/man7/unix.7: Remove mentions of "namespace" in the general sense Günther Noack
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=20261120161202.27163-3-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--cc=alx+linux-man@kernel.org \
--cc=kuniyu@google.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 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.