mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Ian Abbott <abbotti@mev.co.uk>, Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: [ptxdist] [PATCH 0/8] dropbear: version bump and option revise
Date: Mon,  4 Jul 2022 14:18:23 +0200	[thread overview]
Message-ID: <20220704121831.23787-1-ada@thorsis.com> (raw)

Hei hei,

so the important change here is the version bump in the first of the
eight patches.  All the other patches change or fix things which
bugged me over the years.  Since this is touching a security sensitive
service, I would be happy about thorough review.

Greets
Alex

Alexander Dahl (8):
  dropbear: version bump 2020.81 -> 2022.82
  dropbear: Add ed25519 hostkey/public key support
  dropbear: Remove curve25519 dependency
  dropbear: Make Chacha20-Poly1305 encryption optional
  dropbear: Append hints to some menu prompts
  dropbear: Rework key exchange algorithm options
  dropbear: Add conditional comments with warnings
  dropbear: Move option groups to sub menus

 projectroot/etc/init.d/dropbear      |   3 +
 projectroot/etc/rc.once.d/dropbear   |   3 +
 projectroot/usr/lib/init/dropbear.sh |   1 +
 rules/dropbear.in                    | 142 ++++++++++++++++++++-------
 rules/dropbear.make                  |  74 ++++++++++----
 5 files changed, 170 insertions(+), 53 deletions(-)


base-commit: 7384b37919cb66e12ff15b4264325cb5eba911c3
-- 
2.30.2




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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 12:18 Alexander Dahl [this message]
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
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=20220704121831.23787-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=abbotti@mev.co.uk \
    --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