From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 3/4] keyrings.7: document description restriction for logon keys
Date: Mon, 11 Sep 2017 05:11:12 +0200 [thread overview]
Message-ID: <20170911031112.GA5300@asgard.redhat.com> (raw)
"logon" type has additional check that enforces colon-separated prefix in key
descriptions.
* man7/keyrings.7 (.SS Key types) <.TP .IR """logon""">: Document
restriction imposed on logon key descriptions.
Signed-off-by: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
man7/keyrings.7 | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 6f2581c..9a4478e 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -142,6 +142,11 @@ operation),
meaning that the key payload is never visible from user space.
This is suitable for storing username-password pairs
that should not be readable from user space.
+.IP
+Key description of a logon key must start with non-empty colon-delimited
+prefix with the purpose to identify the service to which it belongs.
+(contrary to keys of the "user" type, where this practice is recommended
+but is not enforced).
.TP
.IR """big_key""" " (since Linux 3.13)"
.\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-09-11 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 3:11 Eugene Syromyatnikov [this message]
[not found] ` <20170911031112.GA5300-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-11 14:25 ` [PATCH 3/4] keyrings.7: document description restriction for logon keys Michael Kerrisk (man-opages)
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=20170911031112.GA5300@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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