Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Migration to OpenSSL 1.1.1?
Date: Tue, 15 Jan 2019 13:56:40 +0100	[thread overview]
Message-ID: <20190115135640.762d0d4d@windsurf> (raw)
In-Reply-To: <CANQCQpYePwq3HHJxOjE3F=EFzp0=-AfPUL+KX0gtXyOrHU5p4A@mail.gmail.com>

Hello,

+Peter in Cc.

On Tue, 15 Jan 2019 06:17:28 -0600, Matthew Weber wrote:

> On Tue, Jan 15, 2019 at 4:30 AM Marcel Patzlaff <M.Patzlaff@pilz.de> wrote:
> >
> > Hello,
> >
> > after reading https://www.openssl.org/source/ (especially the part where
> > the version support is stated), the following question pops up:
> > Are there plans to migrate the openssl package to 1.1.1?  
> 
> 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 ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-01-15 12:56 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 [this message]
2019-01-15 13:22     ` Peter Korsgaard

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=20190115135640.762d0d4d@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox