mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: ptxdist@pengutronix.de, mtr@pengutronix.de
Subject: Re: [ptxdist] [PATCH] sshpass: fix a few typos in help text
Date: Fri, 17 Nov 2023 16:15:47 +0100	[thread overview]
Message-ID: <20231117-petty-glaring-baff180d729d@ifak-system.com> (raw)
In-Reply-To: <20231117145055.751524-1-m.tretter@pengutronix.de>

Hello Michael,

Am Fri, Nov 17, 2023 at 03:50:55PM +0100 schrieb Michael Tretter:
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
>  rules/sshpass.in | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> 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.

Reviewed-by: Alexander Dahl <ada@thorsis.com>

Greets
Alex

> -- 
> 2.39.2
> 
> 



  reply	other threads:[~2023-11-17 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 14:50 Michael Tretter
2023-11-17 15:15 ` Alexander Dahl [this message]
2023-11-28  8:36 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20231117-petty-glaring-baff180d729d@ifak-system.com \
    --to=ada@thorsis.com \
    --cc=m.tretter@pengutronix.de \
    --cc=mtr@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