From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Migration to OpenSSL 1.1.1?
Date: Tue, 15 Jan 2019 14:22:40 +0100 [thread overview]
Message-ID: <87a7k2rr6n.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190115135640.762d0d4d@windsurf> (Thomas Petazzoni's message of "Tue, 15 Jan 2019 13:56:40 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
>> There are some efforts starting to bump to the latest stable 1.1.1.
>> We're hoping we can get things bumped before things freeze for the
>> next release.
> The freeze for 2019.02 is going to happen at the end of January, I am
> not sure this leaves us enough time to fix all the consequences of a
> bump to OpenSSL 1.1.1.
> However, since 2019.02 is going to be a LTS maintained for one year,
> perhaps we want to have OpenSSL 1.1.1 in that LTS, knowing that it will
> be maintained, while older OpenSSL versions might not. Is there any
> information available on whether OpenSSL still maintains 1.0.x ? Peter,
> what do you think ?
The official policy is listed here:
https://www.openssl.org/policies/releasestrat.html
So it will be supported almost (but not completely) until the end of the
2019.02 maintenance cycle.
Given how close we are to RC1, I would suggest we stick to 1.0.2 for
2019.02.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-15 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 10:19 [Buildroot] Migration to OpenSSL 1.1.1? Marcel Patzlaff
2019-01-15 12:17 ` Matthew Weber
2019-01-15 12:56 ` Thomas Petazzoni
2019-01-15 13:22 ` Peter Korsgaard [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=87a7k2rr6n.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.