Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: fix for CVE-2015-1794
Date: Wed, 9 Dec 2015 15:33:11 +0200	[thread overview]
Message-ID: <56682D97.1050101@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZR3Jy8rvGQEsjGquZXKHpFnhSqWgHNh4k711xnLJqw2Q@mail.gmail.com>

On 12/09/2015 01:52 PM, Burton, Ross wrote:

> This patch needs to have your (or whoever actually did the work)
> signed-off-by inside the patch, alongside the Upstream-Status.

Also, it's been fixed in openssl 1.0.2e with a bunch of other CVEs - 
I'll send an update for that shortly.

Generally, for oe-core master we always prefer an update to latest 
upstream instead of adding backported patches.

Alex


  reply	other threads:[~2015-12-09 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  2:03 [PATCH] openssl: fix for CVE-2015-1794 Fan Xin
2015-12-09 11:52 ` Burton, Ross
2015-12-09 13:33   ` Alexander Kanavin [this message]
2015-12-10  2:58   ` Fan Xin
2015-12-11  7:24   ` [PATCH v2][jethro] " Fan Xin

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=56682D97.1050101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox