From: Chen Qi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH V2 0/3] systemd: backport patches to fix 3 CVEs
Date: Fri, 2 Nov 2018 12:42:40 +0800 [thread overview]
Message-ID: <cover.1541133621.git.Qi.Chen@windriver.com> (raw)
Changes in V2:
* fix the cve tag problem in the included patch
* use the patches from systemd-stable repo instead of the systemd repo
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 ChenQi/systemd-CVEs
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/systemd-CVEs
Chen Qi (3):
systemd: fix CVE-2018-15686
systemd: fix CVE-2018-15687
systemd: fix CVE-2018-15688
...sive-let-s-rework-the-recursive-logic-to-.patch | 219 ++++++++++++++++++
...eserializing-state-always-use-read_line-L.patch | 250 +++++++++++++++++++++
...sure-we-have-enough-space-for-the-DHCP6-o.patch | 39 ++++
meta/recipes-core/systemd/systemd_239.bb | 3 +
4 files changed, 511 insertions(+)
create mode 100644 meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
--
1.9.1
next reply other threads:[~2018-11-02 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 4:42 Chen Qi [this message]
2018-11-02 4:42 ` [PATCH 1/3] systemd: fix CVE-2018-15686 Chen Qi
2018-11-02 4:42 ` [PATCH 2/3] systemd: fix CVE-2018-15687 Chen Qi
2018-11-02 4:42 ` [PATCH 3/3] systemd: fix CVE-2018-15688 Chen Qi
2018-11-02 5:03 ` ✗ patchtest: failure for systemd: backport patches to fix 3 CVEs (rev2) Patchwork
2018-11-02 6:37 ` ChenQi
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.1541133621.git.Qi.Chen@windriver.com \
--to=qi.chen@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