From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dropbear: security bump version to 2026.92
Date: Fri, 17 Jul 2026 17:47:35 +0200 [thread overview]
Message-ID: <20260717154735.192149-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260707185207.2387124-1-bernd@kuhls.net>
In reply of:
> https://matt.ucc.asn.au/dropbear/CHANGES
>
> - Security: server: Don't allow -B (accept blank password) with
> -t (two factor auth). If run with -t and -B a user configured with a
> blank password would be allowed to log in without pubkey auth.
> https://github.com/mkj/dropbear/commit/23ec78285639edf068d86bb96f91cba755039740
> Reported by nvidia
>
> - Security: server: Fix parsing of long authorized_keys lines.
> The remainder of a long line would be handled as the start of a new line.
> In the case where external programs add semi-trusted public keys to
> authorized_keys, a crafted key might bypass restrictions such as "command=".
> https://github.com/mkj/dropbear/commit/8d8e1930b866eb44135ae393a793cbeb03b6b9d6
> Reported by nvidia
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to 2025.02.x & 2026.05.x. Thanks
> ---
> Gitlab pipelines passed:
> https://gitlab.com/bkuhls/buildroot/-/commits/ac42a98b3278d90a9a5eacd4f4cf6336879b5158
> with the exception of bootlin-m68k-5208-uclibc which was broken before:
> https://gitlab.com/bkuhls/buildroot/-/commits/345fe196c6f81d16429e5d41185e4a08120562d4
>
> 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 31ac153b89..9df81ea4b5 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 defa924475abf6bc1e74abc00173e46bfdc804bd47caafa14f5a4ef0cc76da34 dropbear-2026.91.tar.bz2
> +sha256 91dcb5234de8dea68dd82c55411c9fc986b457ab58372a780ee8a870419c2f7e dropbear-2026.92.tar.bz2
>
> # License file, locally computed
> sha256 a99ce657d790b761c132ee7e0de18edb437ae6361e536d991c6a12f36e770445 LICENSE
> diff --git a/package/dropbear/dropbear.mk b/package/dropbear/dropbear.mk
> index a7de8432af..e7e6703057 100644
> --- a/package/dropbear/dropbear.mk
> +++ b/package/dropbear/dropbear.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -DROPBEAR_VERSION = 2026.91
> +DROPBEAR_VERSION = 2026.92
> DROPBEAR_SITE = https://matt.ucc.asn.au/dropbear/releases
> DROPBEAR_SOURCE = dropbear-$(DROPBEAR_VERSION).tar.bz2
> DROPBEAR_LICENSE = MIT, BSD-2-Clause, Public domain
> --
> 2.47.3
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-17 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 18:52 [Buildroot] [PATCH 1/1] package/dropbear: security bump version to 2026.92 Bernd Kuhls
2026-07-10 16:28 ` Julien Olivain via buildroot
2026-07-17 15:47 ` Thomas Perale 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=20260717154735.192149-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.perale@mind.be \
/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