All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	Chong Lu <Chong.Lu@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] nss: CVE-2014-1568
Date: Tue, 11 Nov 2014 21:54:45 -0800	[thread overview]
Message-ID: <5462F625.6080207@gmail.com> (raw)
In-Reply-To: <CAJTo0LZKsp1UvRNVMiFobDo92okUwDdjUCMj84Sx2xTjHBvNsw@mail.gmail.com>

Would I upgrade nss for dizzy or backport the cve fix (leaning towards 
back porting).

- armin

On 11/07/2014 04:34 PM, Burton, Ross wrote:
> Hi Chong,
>
> On 6 November 2014 07:50, Chong Lu <Chong.Lu@windriver.com
> <mailto:Chong.Lu@windriver.com>> wrote:
>
>     The following changes since commit
>     0add8abc12b850e38a6ec7dcf2856fab2c0107b6:
>
>        buildtools-tarball: package all of Python (2014-11-05 23:30:49 +0000)
>
>     are available in the git repository at:
>
>        git://git.pokylinux.org/poky-contrib
>     <http://git.pokylinux.org/poky-contrib> chonglu/nss
>     http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/nss
>
>     Chong Lu (1):
>        nss: CVE-2014-1568
>
>
> Sorry, but we've just merged Saul's upgrade of NSS to 3.17 so this
> doesn't apply, and as we're unfrozen now an upgrade to the fixed 3.17.1
> seems like the sensible way forwards.  Could you do this upgrade?
>
> Ross
>
>


  parent reply	other threads:[~2014-11-12  5:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  7:50 [PATCH 0/1] nss: CVE-2014-1568 Chong Lu
2014-11-06  7:50 ` [PATCH 1/1] " Chong Lu
2014-11-08  0:34 ` [PATCH 0/1] " Burton, Ross
2014-11-11  1:50   ` Chong Lu
2014-11-12  5:54   ` akuster808 [this message]
2014-11-12  9:28     ` Burton, Ross

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=5462F625.6080207@gmail.com \
    --to=akuster808@gmail.com \
    --cc=Chong.Lu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.