From: Radu Moisan <radu.moisan@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: Upgrade to v1.0.1e
Date: Mon, 08 Apr 2013 20:00:06 +0300 [thread overview]
Message-ID: <5162F796.8020008@intel.com> (raw)
In-Reply-To: <1365440061.12407.49.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On 04/08/2013 07:54 PM, Richard Purdie wrote:
> On Mon, 2013-04-08 at 19:47 +0300, Radu Moisan wrote:
>> Dropped obolete patches and pulled updates for debian patches
> Isn't there some CVE this upgrade fixes which would be worth a mention
> in here?
With respect to what we had (1.0.0j) Scott pointed out the following
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2686
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0166
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0169
Yocto #3965 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=3965>
Radu
[-- Attachment #2: Type: text/html, Size: 1390 bytes --]
next prev parent reply other threads:[~2013-04-08 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 16:47 [PATCH] openssl: Upgrade to v1.0.1e Radu Moisan
2013-04-08 16:54 ` Richard Purdie
2013-04-08 17:00 ` Radu Moisan [this message]
2013-04-08 18:00 ` Saul Wold
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=5162F796.8020008@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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