mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: bruno.thomsen@gmail.com, bth@kamstrup.com
Subject: [ptxdist] [PATCH] openssl: version bump 1.1.1m -> 1.1.1n
Date: Fri, 25 Mar 2022 06:40:29 +0100	[thread overview]
Message-ID: <20220325054029.71959-1-bruno.thomsen@gmail.com> (raw)

Fixes CVE-2022-0778 and CERT-EU SA2022-017.

https://media.cert.europa.eu/static/SecurityAdvisories/2022/CERT-EU-SA2022-017.pdf

Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
 .../0001-debian-targets.patch                                 | 0
 patches/{openssl-1.1.1m => openssl-1.1.1n}/0002-pic.patch     | 0
 ...003-Set-systemwide-default-settings-for-libssl-users.patch | 0
 patches/{openssl-1.1.1m => openssl-1.1.1n}/series             | 0
 rules/openssl.make                                            | 4 ++--
 5 files changed, 2 insertions(+), 2 deletions(-)
 rename patches/{openssl-1.1.1m => openssl-1.1.1n}/0001-debian-targets.patch (100%)
 rename patches/{openssl-1.1.1m => openssl-1.1.1n}/0002-pic.patch (100%)
 rename patches/{openssl-1.1.1m => openssl-1.1.1n}/0003-Set-systemwide-default-settings-for-libssl-users.patch (100%)
 rename patches/{openssl-1.1.1m => openssl-1.1.1n}/series (100%)

diff --git a/patches/openssl-1.1.1m/0001-debian-targets.patch b/patches/openssl-1.1.1n/0001-debian-targets.patch
similarity index 100%
rename from patches/openssl-1.1.1m/0001-debian-targets.patch
rename to patches/openssl-1.1.1n/0001-debian-targets.patch
diff --git a/patches/openssl-1.1.1m/0002-pic.patch b/patches/openssl-1.1.1n/0002-pic.patch
similarity index 100%
rename from patches/openssl-1.1.1m/0002-pic.patch
rename to patches/openssl-1.1.1n/0002-pic.patch
diff --git a/patches/openssl-1.1.1m/0003-Set-systemwide-default-settings-for-libssl-users.patch b/patches/openssl-1.1.1n/0003-Set-systemwide-default-settings-for-libssl-users.patch
similarity index 100%
rename from patches/openssl-1.1.1m/0003-Set-systemwide-default-settings-for-libssl-users.patch
rename to patches/openssl-1.1.1n/0003-Set-systemwide-default-settings-for-libssl-users.patch
diff --git a/patches/openssl-1.1.1m/series b/patches/openssl-1.1.1n/series
similarity index 100%
rename from patches/openssl-1.1.1m/series
rename to patches/openssl-1.1.1n/series
diff --git a/rules/openssl.make b/rules/openssl.make
index 2b8530e70..c5a9dd022 100644
--- a/rules/openssl.make
+++ b/rules/openssl.make
@@ -17,9 +17,9 @@ PACKAGES-$(PTXCONF_OPENSSL) += openssl
 # Paths and names
 #
 OPENSSL_BASE	:= 1.1.1
-OPENSSL_BUGFIX	:= m
+OPENSSL_BUGFIX	:= n
 OPENSSL_VERSION	:= $(OPENSSL_BASE)$(OPENSSL_BUGFIX)
-OPENSSL_MD5	:= 8ec70f665c145c3103f6e330f538a9db
+OPENSSL_MD5	:= 2aad5635f9bb338bc2c6b7d19cbc9676
 OPENSSL		:= openssl-$(OPENSSL_VERSION)
 OPENSSL_SUFFIX	:= tar.gz
 OPENSSL_URL	:= \
-- 
2.35.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


             reply	other threads:[~2022-03-25  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  5:40 Bruno Thomsen [this message]
2022-03-30  7:25 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20220325054029.71959-1-bruno.thomsen@gmail.com \
    --to=bruno.thomsen@gmail.com \
    --cc=bth@kamstrup.com \
    --cc=ptxdist@pengutronix.de \
    /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