From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: openssl10 unusable for many components
Date: Fri, 18 Aug 2017 21:30:23 +0300 [thread overview]
Message-ID: <6240dfca-820c-ced5-4e78-615b544b9f04@linux.intel.com> (raw)
In-Reply-To: <20170818174114.GA3298@jama>
On 08/18/2017 08:41 PM, Martin Jansa wrote:
> openssl 1.1 goes out of upstream support on 2018-08-31 _more than a year
> before_ 1.0.2 support, see:
>
> https://www.openssl.org/policies/releasestrat.html
> Version 1.1.0 will be supported until 2018-08-31.
> Version 1.0.2 will be supported until 2019-12-31 (LTS).
>
> Given its history of major security vulnerabilities, I hope you'll
> remove openssl-1.1.0 even sooner than openssl-1.0.2.
openssl 1.1.1 should be released as soon as final TLS 1.3 spec is
published. I expect it will go out of support much later than 1.1.0. I
do not expect a situation where 1.0 is supported but 1.1.something is not.
Alex
prev parent reply other threads:[~2017-08-18 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:31 openssl10 unusable for many components Martin Jansa
2017-08-17 11:23 ` Alexander Kanavin
2017-08-17 11:33 ` Richard Purdie
2017-08-17 11:46 ` Martin Jansa
2017-08-17 11:54 ` Alexander Kanavin
2017-08-18 5:56 ` Khem Raj
2017-08-18 10:53 ` Alexander Kanavin
2017-08-18 14:41 ` Khem Raj
2017-08-18 17:29 ` Martin Jansa
2017-08-18 17:56 ` Mark Hatle
2017-08-18 18:41 ` Alexander Kanavin
2017-08-18 18:55 ` Martin Jansa
2017-08-18 19:03 ` Mark Hatle
2017-08-18 18:19 ` Alexander Kanavin
2017-08-21 9:29 ` Richard Purdie
2017-08-21 9:59 ` Martin Jansa
2017-08-18 18:15 ` Alexander Kanavin
2017-08-18 17:41 ` Martin Jansa
2017-08-18 18:30 ` Alexander Kanavin [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-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=6240dfca-820c-ced5-4e78-615b544b9f04@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.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 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.