From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] sshpass: fix a few typos in help text
Date: Tue, 28 Nov 2023 09:36:34 +0100 [thread overview]
Message-ID: <20231128083634.1030354-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231117145055.751524-1-m.tretter@pengutronix.de>
Thanks, applied as 17a0ea0c807f5459c44d90838d64e26c27ecdc7b.
Michael
[sent from post-receive hook]
On Tue, 28 Nov 2023 09:36:33 +0100, Michael Tretter <m.tretter@pengutronix.de> wrote:
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> Message-Id: <20231117145055.751524-1-m.tretter@pengutronix.de>
> Reviewed-by: Alexander Dahl <ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/sshpass.in b/rules/sshpass.in
> index b855016e2340..7c5fc5786e6d 100644
> --- a/rules/sshpass.in
> +++ b/rules/sshpass.in
> @@ -4,13 +4,13 @@ config SSHPASS
> tristate
> prompt "sshpass"
> help
> - Sshpass is a tool for non-interactivly performing password
> + sshpass is a tool for non-interactively performing password
> authentication with SSH's so called "interactive keyboard
> password authentication".
> Most user should use SSH's more secure public key
> - authentiaction instead.
> + authentication instead.
>
> - SECURITY NOTE: There is a reason openssh insists that
> + SECURITY NOTE: There is a reason OpenSSH insists that
> passwords be typed interactively.
> Passwords are harder to store securely and to pass around
> securely between programs.
prev parent reply other threads:[~2023-11-28 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:50 [ptxdist] [PATCH] " Michael Tretter
2023-11-17 15:15 ` Alexander Dahl
2023-11-28 8:36 ` Michael Olbrich [this message]
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=20231128083634.1030354-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.tretter@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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