public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Long, Qin" <qin.long@intel.com>
To: "Woodhouse, David" <david.woodhouse@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ye, Ting" <ting.ye@intel.com>
Subject: Re: [Patch] CryptoPkg/OpensslLib: Upgrade OpenSSL version to 1.0.2j
Date: Thu, 29 Sep 2016 14:30:49 +0000	[thread overview]
Message-ID: <BF2CCE9263284D428840004653A28B6E515351A0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1475140721.45169.500.camel@intel.com>

> -----Original Message-----
> From: Woodhouse, David
> Sent: Thursday, September 29, 2016 5:19 PM
> To: Long, Qin <qin.long@intel.com>; edk2-devel@lists.01.org
> Cc: Ye, Ting <ting.ye@intel.com>
> Subject: Re: [Patch] CryptoPkg/OpensslLib: Upgrade OpenSSL version to
> 1.0.2j
> 
> On Thu, 2016-09-29 at 14:09 +0800, Qin Long wrote:
> > Two official releases (OpenSSL 1.0.2i and 1.0.2j) were available
> > with several severity fixes at 22-Sep-2016 and 26-Sep-2016 with
> > several security fixes. Refer to
> > https://www.openssl.org/news/secadv/20160922.txt and
> > https://www.openssl.org/news/secadv/20160926.txt.
> > This patch is to upgrade the supported OpenSSL version in
> > CryptoPkg/OpensslLib to catch the latest release 1.0.2j.
> 
> Hm, we're ready to move to 1.1.0 now aren't we?
> 

Yeah, the internal evaluations is still on process. I plan to make this at Q4.
(https://github.com/qloong/edk2/tree/dev-openssl-1.1.0xx for more validations)

Before the formal move, we still  use this patch to catch the latest openssl-1.0.2 fixes.

> --
>                   Sent with Evolution's ActiveSync support.
> 
> David Woodhouse                            Open Source Technology Centre
> David.Woodhouse@intel.com                              Intel Corporation

      parent reply	other threads:[~2016-09-29 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29  6:09 [Patch] CryptoPkg/OpensslLib: Upgrade OpenSSL version to 1.0.2j Qin Long
2016-09-29  6:45 ` Ye, Ting
2016-09-29  9:22 ` Laszlo Ersek
2016-09-29 14:22   ` Long, Qin
2016-09-29 19:26     ` Laszlo Ersek
2016-09-30  1:07       ` Long, Qin
     [not found] ` <1475140721.45169.500.camel@intel.com>
2016-09-29 14:30   ` Long, Qin [this message]

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-list 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=BF2CCE9263284D428840004653A28B6E515351A0@SHSMSX103.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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