From: Kang Kai <Kai.Kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] readline: Security Advisory - readline - CVE-2014-2524
Date: Mon, 20 Oct 2014 14:00:47 +0800 [thread overview]
Message-ID: <5444A50F.6070403@windriver.com> (raw)
In-Reply-To: <54447E62.2050905@windriver.com>
On 2014年10月20日 11:15, Kang Kai wrote:
> On 2014年10月16日 19:20, Burton, Ross wrote:
>> On 16 October 2014 10:48, Kai Kang <kai.kang@windriver.com> wrote:
>>> +++ b/meta/recipes-core/readline/readline_6.3.bb
>>> @@ -1,5 +1,7 @@
>>> require readline.inc
>>>
>>> +SRC_URI_append = " file://readline63-003"
>> Doing SRC_URI += is the usual thing to do.
>
> OK. I'll send V2.
Just notice that you have done it. Thanks.
--Kai
>
> Thanks,
> Kai
>
>> Does this CVE also apply
>> to readline 5.2 that we ship as a non-GPLv3 alternative?
>>
>> Ross
>>
>>
>
>
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2014-10-20 6:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 9:48 [PATCH 0/3] CVE fixes of package readline and gnupg Kai Kang
2014-10-16 9:48 ` [PATCH 1/3] readline: Security Advisory - readline - CVE-2014-2524 Kai Kang
2014-10-16 11:20 ` Burton, Ross
2014-10-16 21:31 ` Burton, Ross
2014-10-20 3:15 ` Kang Kai
2014-10-20 6:00 ` Kang Kai [this message]
2015-10-06 8:11 ` Petter Mabäcker
2015-10-06 10:06 ` Burton, Ross
2015-10-06 11:23 ` Petter Mabäcker
2015-10-06 12:58 ` Burton, Ross
2015-10-06 13:43 ` Petter Mabäcker
2015-10-06 14:08 ` Burton, Ross
2015-10-06 15:30 ` Petter Mabäcker
2015-10-08 2:13 ` Kang Kai
2015-10-09 7:14 ` Petter Mabäcker
2015-10-08 4:31 ` Marko Lindqvist
2015-10-09 6:53 ` Petter Mabäcker
2014-10-16 9:48 ` [PATCH 2/3] gnupg: CVE-2013-4242 Kai Kang
2014-10-16 9:48 ` [PATCH 3/3] gnupg_1.4.7: add package config libusb 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=5444A50F.6070403@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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