From: Mark Hatle <mark.hatle@windriver.com>
To: "Tan, Raymond" <raymond.tan@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "Gupta, Rahul KumarXX" <rahul.kumarxx.gupta@intel.com>
Subject: Re: openssl: OpenSSL 1.1.x update
Date: Wed, 5 Oct 2016 21:33:50 -0500 [thread overview]
Message-ID: <a3c142bf-8c0b-3f90-dda9-7f72dd4da1cf@windriver.com> (raw)
In-Reply-To: <F0CA9E243F4F424B836EAC30E41BF4CF5DF514DB@PGSMSX104.gar.corp.intel.com>
On 10/5/16 9:11 PM, Tan, Raymond wrote:
> Greetings, I would like to know if there is any plan / schedule to upgrade to openssl 1.1.0 into OE-core?
Currently 1.0.2 is the LTS version of OpenSSL. 1.1.0 is not scheduled to be LTS.
For the upcoming release (soon), I would NOT expect 1.1.0 to be in it. There
are still too many incompatibilities with other components.
For the next version of OE, I think it is appropriate to include 1.1.0, but I
would also like to maintain 1.0.2 for the time being. (Beside LTS, it also is
still the only way to have FIPS-140-2 module, as there is currently no module in
the 1.1.0 -- and there may not be for a while.)
--Mark
> Thanks!
>
> Raymond Tan
>
next prev parent reply other threads:[~2016-10-06 2:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 2:11 openssl: OpenSSL 1.1.x update Tan, Raymond
2016-10-06 2:33 ` Mark Hatle [this message]
2016-10-06 2:59 ` Khem Raj
2016-10-06 14:21 ` Mark Hatle
2016-10-06 15:22 ` Khem Raj
2016-10-06 15:39 ` Mark Hatle
2016-10-13 10:35 ` Tan, Raymond
2016-10-13 10:49 ` Hatle, Mark
2016-12-13 16:00 ` Alexander Kanavin
2016-10-06 2:44 ` Paul Eggleton
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=a3c142bf-8c0b-3f90-dda9-7f72dd4da1cf@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rahul.kumarxx.gupta@intel.com \
--cc=raymond.tan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox