From: Ross Burton <Ross.Burton@arm.com>
To: "tom.isaacson@teknique.com" <tom.isaacson@teknique.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta][PATCH] Upgrade 9.3p1 to 9.3p2 for CVE-2023-38408
Date: Thu, 3 Aug 2023 07:46:22 +0000 [thread overview]
Message-ID: <F062881A-D80F-498E-9172-599CD429072C@arm.com> (raw)
In-Reply-To: <20230729190505.2711-1-tom.isaacson@teknique.com>
The commit formatting guidelines say that the shortlog should start with the recipe name, so please change the commit message to be something along the lines of:
openssh: upgrade to 9.3p2
You can add more details after the first line.
Thanks,
Ross
> On 29 Jul 2023, at 20:05, Tom Isaacson via lists.openembedded.org <tom.isaacson=teknique.com@lists.openembedded.org> wrote:
>
> Signed-off-by: Tom Isaacson <tom.isaacson@teknique.com>
> ---
> .../openssh/{openssh_9.3p1.bb => openssh_9.3p2.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-connectivity/openssh/{openssh_9.3p1.bb => openssh_9.3p2.bb} (98%)
>
> diff --git a/meta/recipes-connectivity/openssh/openssh_9.3p1.bb b/meta/recipes-connectivity/openssh/openssh_9.3p2.bb
> similarity index 98%
> rename from meta/recipes-connectivity/openssh/openssh_9.3p1.bb
> rename to meta/recipes-connectivity/openssh/openssh_9.3p2.bb
> index 3edc123b9a..5fb2dccdfc 100644
> --- a/meta/recipes-connectivity/openssh/openssh_9.3p1.bb
> +++ b/meta/recipes-connectivity/openssh/openssh_9.3p2.bb
> @@ -26,7 +26,7 @@ SRC_URI = "http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
> file://add-test-support-for-busybox.patch \
> file://7280401bdd77ca54be6867a154cc01e0d72612e0.patch \
> "
> -SRC_URI[sha256sum] = "e9baba7701a76a51f3d85a62c383a3c9dcd97fa900b859bc7db114c1868af8a8"
> +SRC_URI[sha256sum] = "200ebe147f6cb3f101fd0cdf9e02442af7ddca298dffd9f456878e7ccac676e8"
>
> CVE_STATUS[CVE-2007-2768] = "not-applicable-config: This CVE is specific to OpenSSH with the pam opie which we don't build/use here."
>
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#185058): https://lists.openembedded.org/g/openembedded-core/message/185058
> Mute This Topic: https://lists.openembedded.org/mt/100432709/6875888
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ross.burton@arm.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2023-08-03 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 19:05 [meta][PATCH] Upgrade 9.3p1 to 9.3p2 for CVE-2023-38408 Tom Isaacson
2023-08-03 7:46 ` Ross Burton [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=F062881A-D80F-498E-9172-599CD429072C@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.isaacson@teknique.com \
/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