From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a99b73211a06c00e6dd36324a33120da7320c6a4
Date: Tue, 08 Dec 2020 17:34:54 +0000 [thread overview]
Message-ID: <4Cr6kl0dBpz2y05@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 5925 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via a99b73211a06c00e6dd36324a33120da7320c6a4 (commit)
via 591738dc5c867cac63a6301a6c1292c471fb617a (commit)
via 4aae5f819a6a8dc2b2adce83cd63ee96e79666fe (commit)
from 8372d890002df382f814c975a73a70701b523bae (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a99b73211a06c00e6dd36324a33120da7320c6a4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Dec 8 18:33:47 2020 +0100
core153: add openssl to updater
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
commit 591738dc5c867cac63a6301a6c1292c471fb617a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Dec 8 18:27:00 2020 +0100
openssl: update to 1.1.1i
fix: EDIPARTYNAME NULL pointer de-reference (CVE-2020-1971)
Severity: High
The X.509 GeneralName type is a generic type for representing different types
of names. One of those name types is known as EDIPartyName. OpenSSL provides a
function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME
to see if they are equal or not. This function behaves incorrectly when both
GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash
may occur leading to a possible denial of service attack.
OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes:
1) Comparing CRL distribution point names between an available CRL and a CRL
distribution point embedded in an X509 certificate
2) When verifying that a timestamp response token signer matches the timestamp
authority name (exposed via the API functions TS_RESP_verify_response and
TS_RESP_verify_token)
If an attacker can control both items being compared then that attacker could
trigger a crash. For example if the attacker can trick a client or server into
checking a malicious certificate against a malicious CRL then this may occur.
Note that some applications automatically download CRLs based on a URL embedded
in a certificate. This checking happens prior to the signatures on the
certificate and CRL being verified. OpenSSL's s_server, s_client and verify
tools have support for the "-crl_download" option which implements automatic
CRL downloading and this attack has been demonstrated to work against those
tools.
Note that an unrelated bug means that affected versions of OpenSSL cannot parse
or construct correct encodings of EDIPARTYNAME. However it is possible to
construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence
trigger this attack.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
commit 4aae5f819a6a8dc2b2adce83cd63ee96e79666fe
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Dec 8 18:26:37 2020 +0100
kernel: update to 4.14.211
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
.../rootfiles/{oldcore/100 => core/153}/filelists/i586/openssl-sse2 | 0
config/rootfiles/{oldcore/100 => core/153}/filelists/openssl | 0
lfs/linux | 6 +++---
lfs/openssl | 4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
copy config/rootfiles/{oldcore/100 => core/153}/filelists/i586/openssl-sse2 (100%)
copy config/rootfiles/{oldcore/100 => core/153}/filelists/openssl (100%)
Difference in files:
diff --git a/config/rootfiles/core/153/filelists/i586/openssl-sse2 b/config/rootfiles/core/153/filelists/i586/openssl-sse2
new file mode 120000
index 000000000..f424713d6
--- /dev/null
+++ b/config/rootfiles/core/153/filelists/i586/openssl-sse2
@@ -0,0 +1 @@
+../../../../common/i586/openssl-sse2
\ No newline at end of file
diff --git a/config/rootfiles/core/153/filelists/openssl b/config/rootfiles/core/153/filelists/openssl
new file mode 120000
index 000000000..e011a9266
--- /dev/null
+++ b/config/rootfiles/core/153/filelists/openssl
@@ -0,0 +1 @@
+../../../common/openssl
\ No newline at end of file
diff --git a/lfs/linux b/lfs/linux
index 04205ee57..e4467c477 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.210
-ARM_PATCHES = 4.14.210-ipfire0
+VER = 4.14.211
+ARM_PATCHES = 4.14.211-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -79,7 +79,7 @@ objects =$(DL_FILE) \
$(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
arm-multi-patches-$(ARM_PATCHES).patch.xz = $(URL_IPFIRE)/arm-multi-patches-$(ARM_PATCHES).patch.xz
-$(DL_FILE)_MD5 = 84918d49079e7a75b4c2450fa3b4fcb9
+$(DL_FILE)_MD5 = 41241e9508acc9183540db785f78ec78
arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 2b0e8e3ebe9827b2bfed7397b043dbc5
install : $(TARGET)
diff --git a/lfs/openssl b/lfs/openssl
index 84f1d0fa5..16e20b439 100644
--- a/lfs/openssl
+++ b/lfs/openssl
@@ -24,7 +24,7 @@
include Config
-VER = 1.1.1h
+VER = 1.1.1i
THISAPP = openssl-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -87,7 +87,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 53840c70434793127a3574433494e8d3
+$(DL_FILE)_MD5 = 08987c3cf125202e2b0840035efb392c
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-12-08 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4Cr6kl0dBpz2y05@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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