| Message ID | 20230807173433.3261181-1-archana.polampalli@windriver.com |
|---|---|
| State | New |
| Headers | show |
| Series | mickledore][PATCH 1/1] openssh: upgrade 9.3p1 -> 9.3p2 | expand |
This hasn’t even landed in master yet, so it can’t be in mickledore. Also when submitting an upgrade to a stable branch, you need to make a good case for why this is a safe thing to do and nothing will break. For example, listing the changes. If the upgrade is for security reasons it’s often simpler to just cherry-pick the patches. Ross
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 42ce814523..558e027f5d 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" # This CVE is specific to OpenSSH with the pam opie which we don't build/use here CVE_CHECK_IGNORE += "CVE-2007-2768"
Signed-off-by: Archana Polampalli <archana.polampalli@windriver.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%)