From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] openssl security upgrade
Date: Tue, 20 Mar 2012 17:35:26 -0700 [thread overview]
Message-ID: <4F69224E.7050901@intel.com> (raw)
In-Reply-To: <cover.1332266918.git.scott.a.garman@intel.com>
On 03/20/2012 11:10 AM, Scott Garman wrote:
> Hello,
>
> This upgrade to the openssl recipe addresses a security vulnerability,
> CVE-2012-0884. I would like to ensure it gets included in our upcoming
> 1.2 release.
>
> This upgrade has been build-tested on all 5 of our qemu architectures,
> and I have inspected the image and package output to ensure there were
> no significant differences between the output of this recipe upgrade
> and the last version of openssl we were using.
I had forgotten to update the distro_tracking fields with this pull
request - so I've pushed a commit onto this branch to do so.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-03-21 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:10 [PATCH 0/1] openssl security upgrade Scott Garman
2012-03-20 18:11 ` [PATCH 1/1] openssl: upgrade to 1.0.0.h Scott Garman
2012-03-21 0:35 ` Scott Garman [this message]
2012-03-21 14:05 ` [PATCH 0/1] openssl security upgrade Richard Purdie
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=4F69224E.7050901@intel.com \
--to=scott.a.garman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox