From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fix CVEs for openssl
Date: Fri, 2 Nov 2018 16:02:12 +0800 [thread overview]
Message-ID: <cover.1541145029.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
Fix CVEs for openssl:
1.0.2p:
* CVE-2018-0734
1.1.1:
* CVE-2018-0734
* CVE-2018-0735
The following changes since commit 411184bfaa6269bf2926bb2a576c0922958cbbb3:
xserver-xorg: fix CVE-2018-14665 (2018-11-01 13:27:26 +0000)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib kangkai/cve
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/cve
Kai Kang (2):
openssl: fix CVE-2018-0734 for both 1.0.2p and 1.1.1
openssl: fix CVE-2018-0735 for 1.1.1
.../openssl/0002-fix-CVE-2018-0734.patch | 108 ++++++++++++++++++
.../openssl/0003-fix-CVE-2018-0735.patch | 50 ++++++++
.../openssl10/0001-fix-CVE-2018-0734.patch | 33 ++++++
.../openssl/openssl10_1.0.2p.bb | 1 +
.../openssl/openssl_1.1.1.bb | 2 +
5 files changed, 194 insertions(+)
create mode 100644 meta/recipes-connectivity/openssl/openssl/0002-fix-CVE-2018-0734.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/0003-fix-CVE-2018-0735.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl10/0001-fix-CVE-2018-0734.patch
--
2.18.0
next reply other threads:[~2018-11-02 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 8:02 kai.kang [this message]
2018-11-02 8:02 ` [PATCH 1/2] openssl: fix CVE-2018-0734 for both 1.0.2p and 1.1.1 kai.kang
2018-11-02 8:02 ` [PATCH 2/2] openssl: fix CVE-2018-0735 for 1.1.1 kai.kang
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=cover.1541145029.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.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