From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mat Martineau
<mathew.j.martineau-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Stephan Mueller
<smueller-T9tCv8IpfcWELgA04lAiVw@public.gmane.org>,
keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC PATCH 0/5] keyctl.2 updates
Date: Thu, 31 Aug 2017 17:58:16 +0200 [thread overview]
Message-ID: <20170831155816.GA606@asgard.redhat.com> (raw)
Hello.
While trying to add support for the new keyctl features (ability to
provide KDF and ability to restrict addition to the keyring) decoding
to strace, I've noticed that these are not documented, so here is
my initial attempt to document these things. Unfortunately, keys/crypto
infrastructure is quite foreign to me, so these patches definitely need
some improvement.
For the one part is definitely omitted yet is the documentation for the
"asymmetric" key type, which should be a part of keyrings.7, I think.
Eugene Syromyatnikov (5):
keyctl.2: change "is" to "was" in error descriptions
keyctl.2: update kernel documentation path reference
keyrings.7: add pointers to kernel's documentation
keyctl.2: document the ability to provide KDF parameters in
KEYCTL_DH_COMPUTE
keyctl.2: document KEYCTL_RESTRICT_KEYRING operation
man2/keyctl.2 | 216 ++++++++++++++++++++++++++++++++++++++++++++++++++++----
man7/keyrings.7 | 5 ++
2 files changed, 209 insertions(+), 12 deletions(-)
--
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
reply other threads:[~2017-08-31 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170831155816.GA606@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mathew.j.martineau-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smueller-T9tCv8IpfcWELgA04lAiVw@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;
as well as URLs for NNTP newsgroup(s).