all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 61353@debbugs.gnu.org
Subject: [bug#61353] [PATCH] gnu: OpenSSL 3: Update to 3.0.8 [security fixes].
Date: Tue,  7 Feb 2023 21:58:57 +0100	[thread overview]
Message-ID: <2b24b0a1feb65e1f3fbd616f1aefb7c063f50cb8.1675803537.git.leo@famulari.name> (raw)

Fixes CVE-2023-0215, CVE-2023-0216, CVE-2023-0217, CVE-2023-0286, CVE-2023-0401,
CVE-2022-4203, CVE-2022-4304, and CVE-2022-4450.

https://www.openssl.org/news/secadv/20230207.txt

gnu/packages/tls.scm (openssl-3.0): Update to 3.0.8.
---
 gnu/packages/tls.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
index 66c111cb56..9eaa859a57 100644
--- a/gnu/packages/tls.scm
+++ b/gnu/packages/tls.scm
@@ -636,7 +636,7 @@ (define openssl/fixed
 (define-public openssl-3.0
   (package
     (inherit openssl-1.1)
-    (version "3.0.7")
+    (version "3.0.8")
     (source (origin
               (method url-fetch)
               (uri (list (string-append "https://www.openssl.org/source/openssl-"
@@ -649,7 +649,7 @@ (define-public openssl-3.0
               (patches (search-patches "openssl-3.0-c-rehash-in.patch"))
               (sha256
                (base32
-                "0virbkcrw7nn3gr5r51z722gs1ppig0casj0c9pnj3i65829s143"))))
+                "0gjb7qjl2jnzs1liz3rrccrddxbk6q3lg8z27jn1xwzx72zx44vc"))))
     (arguments
      (substitute-keyword-arguments (package-arguments openssl-1.1)
        ((#:phases phases '%standard-phases)
-- 
2.38.1





             reply	other threads:[~2023-02-07 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 20:58 Leo Famulari [this message]
2023-02-11 22:18 ` bug#61353: [PATCH] gnu: OpenSSL 3: Update to 3.0.8 [security fixes] Leo Famulari

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=2b24b0a1feb65e1f3fbd616f1aefb7c063f50cb8.1675803537.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=61353@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.