From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 1/1] package/dropbear: bump version to 2025.87
Date: Sun, 09 Mar 2025 10:15:32 +0200 [thread overview]
Message-ID: <874j02d3h7.fsf@tarshish> (raw)
In-Reply-To: <20250309080905.25158-1-bernd@kuhls.net> (Bernd Kuhls's message of "Sun, 9 Mar 2025 09:09:05 +0100")
Hi Bernd,
On Sun, Mar 09 2025, Bernd Kuhls wrote:
> Changelog: https://matt.ucc.asn.au/dropbear/CHANGES
CHANGES says:
- >> Disable SHA-1 algorithms by default. SHA-1 has known weakness and
most implementations support alternatives.
Can we enable SHA-1 when BR2_PACKAGE_DROPBEAR_LEGACY_CRYPTO is enabled?
baruch
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/dropbear/dropbear.hash | 2 +-
> package/dropbear/dropbear.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/dropbear/dropbear.hash b/package/dropbear/dropbear.hash
> index cf2dd18d61..777910da15 100644
> --- a/package/dropbear/dropbear.hash
> +++ b/package/dropbear/dropbear.hash
> @@ -1,5 +1,5 @@
> # From https://matt.ucc.asn.au/dropbear/releases/SHA256SUM.asc
> -sha256 e78936dffc395f2e0db099321d6be659190966b99712b55c530dd0a1822e0a5e dropbear-2024.86.tar.bz2
> +sha256 738b7f358547f0c64c3e1a56bbc5ef98d34d9ec6adf9ccdf01dc0bf2caa2bc8d dropbear-2025.87.tar.bz2
>
> # License file, locally computed
> sha256 a99ce657d790b761c132ee7e0de18edb437ae6361e536d991c6a12f36e770445 LICENSE
> diff --git a/package/dropbear/dropbear.mk b/package/dropbear/dropbear.mk
> index e043893aa1..4a3931fd18 100644
> --- a/package/dropbear/dropbear.mk
> +++ b/package/dropbear/dropbear.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -DROPBEAR_VERSION = 2024.86
> +DROPBEAR_VERSION = 2025.87
> DROPBEAR_SITE = https://matt.ucc.asn.au/dropbear/releases
> DROPBEAR_SOURCE = dropbear-$(DROPBEAR_VERSION).tar.bz2
> DROPBEAR_LICENSE = MIT, BSD-2-Clause, Public domain
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-03-09 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 8:09 [Buildroot] [PATCH/next 1/1] package/dropbear: bump version to 2025.87 Bernd Kuhls
2025-03-09 8:15 ` Baruch Siach via buildroot [this message]
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=874j02d3h7.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=bernd@kuhls.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