From: Lukas Wunner <lukas@wunner.de>
To: David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org
Subject: [PATCH keyutils] man: keyctl(1): Fix typo pkey_decrypt -> pkey_verify
Date: Mon, 14 Oct 2024 11:54:46 +0200 [thread overview]
Message-ID: <c6db4d5e631df30499b6a34885b5551f2da2436c.1728899510.git.lukas@wunner.de> (raw)
The synopsis of keyctl(1) erroneously lists "pkey_decrypt" not once but
twice. The second occurrence was obviously meant to be "pkey_verify".
Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
man/keyctl.1 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/keyctl.1 b/man/keyctl.1
index c1d067f..67e48b8 100644
--- a/man/keyctl.1
+++ b/man/keyctl.1
@@ -113,7 +113,7 @@ keyctl \- key management facility control
.br
\fBkeyctl\fR pkey_sign <key> <pass> <datafile> [k=v]* ><sigfile>
.br
-\fBkeyctl\fR pkey_decrypt <key> <pass> <datafile> <sigfile> [k=v]*
+\fBkeyctl\fR pkey_verify <key> <pass> <datafile> <sigfile> [k=v]*
.br
\fBkeyctl\fR watch [\-f<filters>] <key>
.br
--
2.43.0
reply other threads:[~2024-10-14 9:54 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=c6db4d5e631df30499b6a34885b5551f2da2436c.1728899510.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=dhowells@redhat.com \
--cc=keyrings@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).