mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de, Alexander Dahl <ada@thorsis.com>
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [PATCH 6/8] dropbear: Rework key exchange algorithm options
Date: Mon, 4 Jul 2022 13:31:10 +0100	[thread overview]
Message-ID: <2c07edab-1c42-7fe3-29d7-ff8e401a40ca@mev.co.uk> (raw)
In-Reply-To: <20220704121831.23787-7-ada@thorsis.com>

On 04/07/2022 13:18, Alexander Dahl wrote:
> The options for diffie-hellman key exchange were mixed up with message
> integrity hmacs.
> 
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> ---
>   rules/dropbear.in   | 43 +++++++++++++++++++++++++++++++++++++++++--
>   rules/dropbear.make | 36 ++++++++++++++++++++++++++++++++----
>   2 files changed, 73 insertions(+), 6 deletions(-)
> 
> diff --git a/rules/dropbear.in b/rules/dropbear.in
> index f7f96a762..043b0e76d 100644
> --- a/rules/dropbear.in
> +++ b/rules/dropbear.in
[snip]
>   config DROPBEAR_CURVE25519
>   	bool
> -	prompt "curve25519-donna"
> +	prompt "curve25519"
>   	help
>   	  Enable curve25519-donna for key exchange.

The name in the prompt now differs from the name in the help text, which 
might be confusing.

>   	  This is another elliptic curve method with good security properties.
>   	  This algorithm does not rely on NIST-based curves
>   	  and gives us more security confidence against a possible
>   	  backdoor in nistp-256 curve.
> +	
> +	  Small systems should generally include either curve25519 or
> +	  ecdh for performance.
> +
> +config DROPBEAR_DH_GROUP1
> +	bool
> +	prompt "group1 (legacy, client only)"
> +	help
> +	  1024 bit, sha1.
> +	  is too small for security though is necessary if you need
> +	  compatibility with some implementations such as Dropbear
> +	  versions < 0.53.
> +	  Client only!

Missing word "This"?

-- 
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company  )=-
-=( registered in England & Wales.  Regd. number: 02862268.  )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-



  reply	other threads:[~2022-07-04 12:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 12:18 [ptxdist] [PATCH 0/8] dropbear: version bump and option revise Alexander Dahl
2022-07-04 12:18 ` [ptxdist] [PATCH 1/8] dropbear: version bump 2020.81 -> 2022.82 Alexander Dahl
2022-07-08 15:13   ` Michael Olbrich
2022-07-21  7:10     ` [ptxdist] [PATCH] dropbear: Add patch to fix build with X11 forwarding Alexander Dahl
2022-08-04 15:14       ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-29  6:23   ` [ptxdist] [APPLIED] dropbear: version bump 2020.81 -> 2022.82 Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 2/8] dropbear: Add ed25519 hostkey/public key support Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 3/8] dropbear: Remove curve25519 dependency Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 4/8] dropbear: Make Chacha20-Poly1305 encryption optional Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 5/8] dropbear: Append hints to some menu prompts Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 6/8] dropbear: Rework key exchange algorithm options Alexander Dahl
2022-07-04 12:31   ` Ian Abbott [this message]
2022-07-08  9:09     ` Michael Olbrich
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 7/8] dropbear: Add conditional comments with warnings Alexander Dahl
2022-07-29  6:23   ` [ptxdist] [APPLIED] " Michael Olbrich
2022-07-04 12:18 ` [ptxdist] [PATCH 8/8] dropbear: Move option groups to sub menus Alexander Dahl
2022-07-29  6:23   ` [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=2c07edab-1c42-7fe3-29d7-ff8e401a40ca@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=ada@thorsis.com \
    --cc=bruno.thomsen@gmail.com \
    --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