From: Scott Garman <scott.a.garman@intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 2/4] libuser: Upgrade from 0.56.18 to 0.57.1
Date: Thu, 27 Jan 2011 07:59:51 -0800 [thread overview]
Message-ID: <4D419677.6080100@intel.com> (raw)
In-Reply-To: <600acc9d3bd9271836ab244de7c072ffe11caec2.1296105920.git.edwin.zhai@intel.com>
On 01/26/2011 09:29 PM, poky-bounces@yoctoproject.org wrote:
> From: Zhai Edwin<edwin.zhai@intel.com>
>
> This can fix the vulnerable issue @ http://secunia.com/advisories/42891/
This isn't a big deal at the moment, but I'm thinking about establishing
a best practice going forward to document security-related fixes. The
CVE number is regarded as the universal identifier, so something like
the following is preferred:
* Addresses CVE-2011-0002
The important thing is to include the CVE identifier(s) somewhere in the
commit log - I may end up developing some tools for extracting that
information from our commits in the future.
Just FYI for now - this isn't documented anywhere yet.
Thanks,
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
Intel Open Source Technology Center
parent reply other threads:[~2011-01-27 15:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <600acc9d3bd9271836ab244de7c072ffe11caec2.1296105920.git.edwin.zhai@intel.com>]
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=4D419677.6080100@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@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.