From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH] 3/5] bzip2: Security fix CVE-2016-3189
Date: Mon, 8 Aug 2016 15:41:23 +0300 [thread overview]
Message-ID: <f399842d-e37d-35ff-e8bc-bfac3f37f47c@linux.intel.com> (raw)
In-Reply-To: <1468710255-5030-3-git-send-email-akuster808@gmail.com>
On 07/17/2016 02:04 AM, Armin Kuster wrote:
> +Upstream-Status: Backport
> +https://bugzilla.suse.com/attachment.cgi?id=681334
> +
> +CVE: CVE-2016-3189
Backport means the patch is taken from upstream development repository,
and it's also good to provide a link to where it is in the upstream.
This looks like a distro vendor fix, so the upstream-status should be
either pending or inappropriate (depending on the upstream development
situation).
Alex
next prev parent reply other threads:[~2016-08-08 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 23:04 [master][PATCH] 1/5] openssl: Security fix CVE-2016-2177 Armin Kuster
2016-07-16 23:04 ` [master][PATCH] 2/5] openssl: Security fix CVE-2016-2178 Armin Kuster
2016-07-16 23:04 ` [master][PATCH] 3/5] bzip2: Security fix CVE-2016-3189 Armin Kuster
2016-08-08 12:41 ` Alexander Kanavin [this message]
2016-07-16 23:04 ` [master][PATCH] 4/5] python2: Security fix CVE-2016-5636 Armin Kuster
2016-07-16 23:04 ` [master][PATCH] 5/5] python3: " Armin Kuster
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=f399842d-e37d-35ff-e8bc-bfac3f37f47c@linux.intel.com \
--to=alexander.kanavin@linux.intel.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 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.