From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] package/glibc: bump to 2.27
Date: Tue, 06 Feb 2018 00:32:38 +0100 [thread overview]
Message-ID: <87607bui5l.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180205214157.GC2806@scaer> (Yann E. MORIN's message of "Mon, 5 Feb 2018 22:41:57 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Baruch, All,
> On 2018-02-05 23:01 +0200, Baruch Siach spake thusly:
>> On Mon, Feb 05, 2018 at 09:57:16PM +0100, Romain Naour wrote:
>> > See: https://sourceware.org/ml/libc-announce/2018/msg00000.html
>> > https://sourceware.org/glibc/wiki/Release/2.27
>> Note that this is a security bump fixing CVE-2017-1000408, CVE-2017-1000409,
>> CVE-2017-16997, CVE-2018-1000001, and CVE-2018-6485.
> There are 10 CVE listed in the release annoucement mail, but you list
> only five here. Why only those?
> Do we want to list all the CVEs fixed in a release? And if we don't list
> all, why do we even list only a subset?
> I don't think we should, especially since the release mail is linked to
> the commit log and has all the details.
For security bumps we normally DO list the CVEs for ease of use, E.G.:
commit d52cd750c762c78ebcf8623fab8a9c43c9419625
Author: Peter Korsgaard <peter@korsgaard.com>
Date: Sun Jan 28 20:23:02 2018 +0100
wireshark: security bump to version 2.2.12
Fixes the following security issues:
CVE-2017-17997: MRDISC dissector crash
https://www.wireshark.org/security/wnpa-sec-2018-02.html
CVE-2018-5334: IxVeriWave file parser crash
https://www.wireshark.org/security/wnpa-sec-2018-03.html
CVE-2018-5335: WCP dissector crash
https://www.wireshark.org/security/wnpa-sec-2018-04.html
CVE-2018-5336: Multiple dissectors could crash
https://www.wireshark.org/security/wnpa-sec-2018-01.html
For more information, see the release notes:
https://www.wireshark.org/docs/relnotes/wireshark-2.2.12.html
While we are at it, also add as hash for license file.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
So I prefer to do that as well here.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-05 23:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:57 [Buildroot] [PATCH 1/5] package/x11r7/xlib_libxshmfence: fix build with glibc 2.27 Romain Naour
2018-02-05 20:57 ` [Buildroot] [PATCH 2/5] package/pulseaudio: only define memfd_create() if not already defined Romain Naour
2018-02-05 20:57 ` [Buildroot] [PATCH 3/5] package/libraw: rename internal powf64 Romain Naour
2018-02-05 20:57 ` [Buildroot] [PATCH 4/5] package/glibc: remove GLIBC_SRC_SUBDIR Romain Naour
2018-02-05 21:27 ` Yann E. MORIN
2018-02-05 20:57 ` [Buildroot] [PATCH 5/5] package/glibc: bump to 2.27 Romain Naour
2018-02-05 21:01 ` Baruch Siach
2018-02-05 21:16 ` Romain Naour
2018-02-05 21:41 ` Yann E. MORIN
2018-02-05 23:32 ` Peter Korsgaard [this message]
2018-02-06 4:15 ` Baruch Siach
2018-02-06 8:18 ` Arnout Vandecappelle
2018-02-06 10:50 ` Baruch Siach
2018-02-06 12:38 ` Arnout Vandecappelle
2018-02-06 13:44 ` Peter Korsgaard
2018-02-06 13:46 ` Baruch Siach
2018-02-06 14:41 ` Peter Korsgaard
2018-02-06 16:40 ` Baruch Siach
2018-02-05 21:08 ` [Buildroot] [PATCH 1/5] package/x11r7/xlib_libxshmfence: fix build with glibc 2.27 Yann E. MORIN
2018-02-06 12:43 ` Thomas Petazzoni
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=87607bui5l.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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