From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] dropbear: version bump 2025.88 -> 2025.89
Date: Mon, 27 Apr 2026 09:46:11 +0200 [thread overview]
Message-ID: <20260427074611.52614-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260420110451.141525-2-ada@thorsis.com>
Thanks, applied as 5b03b78561834d2b80e1ea6209caf8eef554f1c8.
Michael
[sent from post-receive hook]
On Mon, 27 Apr 2026 09:46:11 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> Security update, plugs CVE-2025-14282 and CVE-2019-6111.
> Plus some minor bugfixes.
>
> Link: https://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2025q4/002390.html
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20260420110451.141525-2-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/dropbear.make b/rules/dropbear.make
> index 79cb8873e3e1..fe44432c97cb 100644
> --- a/rules/dropbear.make
> +++ b/rules/dropbear.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_DROPBEAR) += dropbear
> #
> # Paths and names
> #
> -DROPBEAR_VERSION := 2025.88
> -DROPBEAR_MD5 := 510165167b102589d64144cab4477b6c
> +DROPBEAR_VERSION := 2025.89
> +DROPBEAR_MD5 := 2816ff711130f030daee12cbb10fd5ec
> DROPBEAR := dropbear-$(DROPBEAR_VERSION)
> DROPBEAR_SUFFIX := tar.bz2
> DROPBEAR_URL := \
next prev parent reply other threads:[~2026-04-27 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 11:04 [ptxdist] [PATCH 0/2] dropbear: version bump and cve product adaption Alexander Dahl via ptxdist
2026-04-20 11:04 ` [ptxdist] [PATCH 1/2] dropbear: version bump 2025.88 -> 2025.89 Alexander Dahl via ptxdist
2026-04-27 7:46 ` Michael Olbrich [this message]
2026-04-20 11:04 ` [ptxdist] [PATCH 2/2] dropbear: add custom CVE product Alexander Dahl via ptxdist
2026-04-27 7:46 ` [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=20260427074611.52614-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.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