From: dogedoge61@gmail.com
To: 9front@9front.org
Subject: [9front] [PATCH] aescbc(1) correction
Date: Wed, 15 Sep 2021 15:11:49 -0400 [thread overview]
Message-ID: <2AB663B12C5F23BFDAC1087D871EAABF@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
the description of the -i option says it reads the password from standard input.
this is wrong. it reads the password from file descriptor 3.
this patch corrects this
- binarycat
[-- Attachment #2: Type: text/plain, Size: 306 bytes --]
--- //.git/fs/object/8f4842d3465e96d264f5c2f7fa2d61db871aae9f/tree/sys/man/1/secstore
+++ sys/man/1/secstore
@@ -68,7 +68,7 @@
.PP
Option
.B -i
-says that the password should be read from standard input
+says that the password should be read from file descriptor 3
instead of from
.BR /dev/cons .
.PP
next reply other threads:[~2021-09-18 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 19:11 dogedoge61 [this message]
2021-09-15 15:33 ` binary cat
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=2AB663B12C5F23BFDAC1087D871EAABF@gmail.com \
--to=dogedoge61@gmail.com \
--cc=9front@9front.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).