public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] openssl: update to 1.1.1g
Date: Tue, 21 Apr 2020 15:09:41 +0100	[thread overview]
Message-ID: <7BF54C8D-27B9-4E17-9CCA-8F1A93F58A32@ipfire.org> (raw)
In-Reply-To: <20200421134338.29148-1-arne_f@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

Hello Arne,

Thank you very much for patching this so quickly.

Best,
-Michael

> On 21 Apr 2020, at 14:43, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
> 
> CVE-2020-1967 (OpenSSL advisory) [High severity] 21 April 2020:
>    Server or client applications that call the SSL_check_chain()
>    function during or after a TLS 1.3 handshake may crash due
>    to a NULL pointer dereference as a result of incorrect handling
>    of the "signature_algorithms_cert" TLS extension.
>    The crash occurs if an invalid or unrecognised signature algorithm
>    is received from the peer. This could be exploited by a malicious
>    peer in a Denial of Service attack.
> https://www.openssl.org/news/secadv/20200421.txt
> 
> Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
> ---
> lfs/openssl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/openssl b/lfs/openssl
> index 06b999a15..8fe3c2856 100644
> --- a/lfs/openssl
> +++ b/lfs/openssl
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 1.1.1f
> +VER        = 1.1.1g
> 
> THISAPP    = openssl-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -87,7 +87,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 3f486f2f4435ef14b81814dbbc7b48bb
> +$(DL_FILE)_MD5 = 76766e98997660138cdaf13a187bd234
> 
> install : $(TARGET)
> 
> -- 
> 2.17.1
> 


      reply	other threads:[~2020-04-21 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:43 Arne Fitzenreiter
2020-04-21 14:09 ` Michael Tremer [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=7BF54C8D-27B9-4E17-9CCA-8F1A93F58A32@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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