All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/dropbear: bump to version 2020.79
Date: Tue, 23 Jun 2020 08:19:25 +0200	[thread overview]
Message-ID: <875zbi8fte.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200622105151.rrcjmjdqxiy5pcgp@falbala.internal.home.lespocky.de> (Alexander Dahl's message of "Mon, 22 Jun 2020 12:51:52 +0200")

>>>>> "Alexander" == Alexander Dahl <post@lespocky.de> writes:

 > Hei hei,
 > On Mon, Jun 22, 2020 at 11:07:36AM +0200, Peter Korsgaard wrote:
 >> >>>>> "Francois" == Francois Perrad <fperrad@gmail.com> writes:
 >> 
 >> > CBC ciphers, 3DES and hmac-sha1-96 are now disabled by default.
 >> 
 >> Do we expect that to cause compatibility issues?

 > I just looked in package/dropbear/dropbear.mk and those options are
 > explicitly disabled if DROPBEAR_DISABLE_LEGACY_CRYPTO is set. From a

You mean NOT set (ifndef).

 > quick glance I would say now there's no possibility to activate those
 > anymore.

Indeed. Presumably we need to handle the case where the option is set to
ensure you end up with the configuration as described in the help text:

          Enable legacy and possibly insecure algorithms:
            3DES encryption
            SHA1-96 message integrity
            CBC encryption mode
            DSA public keys
            Diffie-Hellman Group1 key exchange

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2020-06-23  6:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  7:39 [Buildroot] [PATCH] package/dropbear: bump to version 2020.79 Francois Perrad
2020-06-22  9:07 ` Peter Korsgaard
2020-06-22 10:51   ` Alexander Dahl
2020-06-22 18:48     ` François Perrad
2020-06-23  6:24       ` Peter Korsgaard
2020-06-23  6:19     ` Peter Korsgaard [this message]
2020-08-04 10:15   ` Thomas De Schampheleire
2020-08-04 11:40     ` Peter Korsgaard
2020-08-04 13:24       ` Thomas De Schampheleire

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=875zbi8fte.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.