From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] dropbear: add custom CVE product
Date: Mon, 27 Apr 2026 09:46:12 +0200 [thread overview]
Message-ID: <20260427074612.52656-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260420110451.141525-3-ada@thorsis.com>
Thanks, applied as c242239db991742d4a4ba202e4ab1afd265dcfa2.
Michael
[sent from post-receive hook]
On Mon, 27 Apr 2026 09:46:12 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> The autogenerated one does not match.
>
> Link: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&orderBy=CPEURI&keyword=dropbear&status=FINAL&startIndex=60
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20260420110451.141525-3-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/dropbear.make b/rules/dropbear.make
> index fe44432c97cb..921aeb9ad5fc 100644
> --- a/rules/dropbear.make
> +++ b/rules/dropbear.make
> @@ -32,6 +32,7 @@ DROPBEAR_LICENSE_FILES := \
> file://libtomcrypt/LICENSE;md5=71baacc459522324ef3e2b9e052e8180 \
> file://libtommath/LICENSE;md5=23e7e0a32e53a2b1d35f5fd9ef053402 \
> file://src/loginrec.c;startline=1;endline=26;md5=0d785ee11fab1cead2c7fee9c35574f1
> +DROPBEAR_CVE_PRODUCT := dropbear_ssh_project:dropbear_ssh
>
> # ----------------------------------------------------------------------------
> # Prepare
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 ` [ptxdist] [APPLIED] " Michael Olbrich
2026-04-20 11:04 ` [ptxdist] [PATCH 2/2] dropbear: add custom CVE product Alexander Dahl via ptxdist
2026-04-27 7:46 ` Michael Olbrich [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=20260427074612.52656-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