public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <randy.macleod@windriver.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] openssl: upgrade from 1.1.1k to 1.1.1l
Date: Wed, 25 Aug 2021 05:27:42 +0000	[thread overview]
Message-ID: <YSXUzcngsQ2T+0KE@korppu> (raw)
In-Reply-To: <20210825034405.142072-1-Randy.MacLeod@windriver.com>

Hi,

On Tue, Aug 24, 2021 at 11:44:05PM -0400, Randy MacLeod wrote:
> Includes fixes for:
> 
> CVE: CVE-2021-3711
> CVE: CVE-2021-3712
> 
> as described by:
>    https://www.openssl.org/news/secadv/20210824.txt
> 
> Ptest results on qemux86-64 with kvm:
>    All tests successful.
>    Files=158, Tests=2532, 137 wallclock secs \
>      ( 2.59 usr  0.33 sys + 104.71 cusr 44.19 csys = 151.82 CPU)
>    Result: PASS
>    DURATION: 137

I sent the same with CI test runs passing on x86_86 and aarch64 products
on dunfell. No problems seen with the update.

Tested-by: Mikko Rapeli <mikko.rapeli@bmw.de>

-Mikko

> Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> ---
>  .../openssl/{openssl_1.1.1k.bb => openssl_1.1.1l.bb}            | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-connectivity/openssl/{openssl_1.1.1k.bb => openssl_1.1.1l.bb} (98%)
> 
> diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1k.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
> similarity index 98%
> rename from meta/recipes-connectivity/openssl/openssl_1.1.1k.bb
> rename to meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
> index 09afa27ac1..b241ba78bc 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.1.1k.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1l.bb
> @@ -28,7 +28,7 @@ SRC_URI:append:riscv32 = " \
>             file://0004-Fixup-support-for-io_pgetevents_time64-syscall.patch \
>             "
>  
> -SRC_URI[sha256sum] = "892a0875b9872acd04a9fde79b1f943075d5ea162415de3047c327df33fbaee5"
> +SRC_URI[sha256sum] = "0b7a3e5e59c34827fe0c3a74b7ec8baef302b98fa80088d7f9153aa16fa76bd1"
>  
>  inherit lib_package multilib_header multilib_script ptest
>  MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
> -- 
> 2.30.2
> 

> 
> 
> 

      reply	other threads:[~2021-08-25  5:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  3:44 [PATCH] openssl: upgrade from 1.1.1k to 1.1.1l Randy MacLeod
2021-08-25  5:27 ` Mikko Rapeli [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=YSXUzcngsQ2T+0KE@korppu \
    --to=mikko.rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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