From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Does CVE-2015-7547 affect eglibc?
Date: Wed, 24 Feb 2016 10:38:11 -0600 [thread overview]
Message-ID: <56CDDC73.1000000@windriver.com> (raw)
In-Reply-To: <56CCF5E8.3000005@gmail.com>
On 2/23/16 6:14 PM, akuster808 wrote:
>
>
> On 02/23/2016 02:52 PM, Darcy Watkins wrote:
>> On Tue, 2016-02-23 at 13:51 -0800, Mark Hatle wrote:
>>> On 2/23/16 1:53 PM, Khem Raj wrote:
>>>> On Tue, Feb 23, 2016 at 2:25 PM, Darcy Watkins
>>>>> CVE-2015-7547 glibc vulnerability has been published as affecting glibc
>>>>> since ver 2.9 (fixed in 2.23 and patched in 2.22 and 2.21).
>>>>>
>>>>> Anyone know if we need the same security fixes in eglibc?
>>>>
>>>> yes you do. Eglibc was nothing but glibc+few fixes.
>>>
>>> Yes this affects all eglibc version 2.9 and newer up to glibc 2.23.
>>>
>>> As far as I'm aware, this affects all Yocto Project versions up to 2.0.
>>
>> I will be interested in knowing which Yocto Project versions will
>> receive the fixes.
>
> Master, 2.0 and 1.8 all have the fixes.
> How far back do we go in matters like this?
Official support is current (in development) and the last two releases. So up
to about a year and a half of support.
After this point, it becomes community support. This really means, if someone
in the community wants to continue support past the YP's support guidelines they
are welcome to do so -- but there won't be any official releases, only checkins
to the repository.
We have done this on some OpenSSL fixes in the past, but it was based on
specific requests and people submitting the fixes to be included with older
versions.
> 1.7 (dizzy) I plan on doing soon. beyond that I do not know. those are
> all community supported.
>
> - armin
>>
>> Thanks in advance!
>>
>>> (The patch referenced by the security announcement applies to all of the
>>> versions of glibc I've needed to apply it to for my customers. A few per-line
>>> tweaks might be necessary, but it was fairly easy.)
>>
>>
next prev parent reply other threads:[~2016-02-24 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 19:25 Does CVE-2015-7547 affect eglibc? Darcy Watkins
2016-02-23 19:53 ` Khem Raj
2016-02-23 21:51 ` Mark Hatle
2016-02-23 22:52 ` Darcy Watkins
2016-02-24 0:14 ` akuster808
2016-02-24 16:38 ` Mark Hatle [this message]
2016-02-24 16:50 ` akuster808
2016-02-26 1:43 ` Darcy Watkins
2016-02-26 7:52 ` Khem Raj
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=56CDDC73.1000000@windriver.com \
--to=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.