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:24:25 +0200 [thread overview]
Message-ID: <871rm68fl2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAB0FRsve+Jsqyf-fPdwV6=WJLObETo=v5k9JtP-9c9csvPP1OQ@mail.gmail.com> ("François Perrad"'s message of "Mon, 22 Jun 2020 20:48:57 +0200")
>>>>> "Fran?ois" == Fran?ois Perrad <francois.perrad@gadz.org> writes:
> Le lun. 22 juin 2020 ? 12:52, Alexander Dahl <post@lespocky.de> a ?crit :
>> 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
>> quick glance I would say now there's no possibility to activate those
>> anymore.
>>
>>
> BR2_PACKAGE_DROPBEAR_LOCALOPTIONS_FILE allows to build any custom configuration.
> maybe we can remove BR2_PACKAGE_DROPBEAR_LEGACY_CRYPTO (which is less
> versatile) ?
> see https://git.busybox.net/buildroot/commit/package/dropbear/Config.in?id=72d4d098b0dbb10d3904868acc11c97acafa8d80
> see https://git.busybox.net/buildroot/commit/package/dropbear/Config.in?id=26708469adc3f5e4194f176fa51f1ce280b0b357
We could, but then we would end up changing the configuration for
everyone not using such a file (E.G. DROPBEAR_DSS /
DROPBEAR_DH_GROUP1).
We already do a bunch of fixups in localoptions.h, so I think just
correcting BR2_PACKAGE_DROPBEAR_LEGACY_CRYPTO to do what it is supposed
to do after the version bump is nicer.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-06-23 6:24 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 [this message]
2020-06-23 6:19 ` Peter Korsgaard
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=871rm68fl2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox