All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mikko.Rapeli@bmw.de
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to backport openssl to Sumo
Date: Thu, 21 Nov 2019 01:05:55 +0200	[thread overview]
Message-ID: <20191120230555.GA3962@localhost> (raw)
In-Reply-To: <20191120213951.GA3527@hiutale>

On Wed, Nov 20, 2019 at 09:39:51PM +0000, Mikko.Rapeli@bmw.de wrote:
>...
> I could submit these too if someone wants to setup a communit maintenance branch for sumo.

I would not consider this appropriate for a stable branch. With such 
invasive changes it would no longer be reasonably safe for users to 
follow the branch to receive security updates for other recipes.

In Ubuntu 18.04 security support for OpenSSL 1.0.2 is provided until at 
least April 2023. Similar schedules exist for other LTS distributions.
This provides sources for piggy-backing security support for a few years
after upstream support ends.

> Cheers,
> 
> -Mikko

cu
Adrian


  reply	other threads:[~2019-11-20 23:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 18:18 How to backport openssl to Sumo Ryan Harkin
2019-11-20 18:28 ` Ross Burton
2019-11-20 18:59   ` Ryan Harkin
2019-11-20 18:36 ` Mark Hatle
2019-11-20 19:06   ` Ryan Harkin
2019-11-20 19:09     ` Mark Hatle
2019-11-20 19:27       ` Andre McCurdy
2019-11-20 19:44         ` Ryan Harkin
2019-11-20 19:57           ` Andre McCurdy
2019-11-20 21:29       ` Ryan Harkin
2019-11-20 22:41         ` Ryan Harkin
2019-11-20 23:53           ` Andre McCurdy
2019-11-21  8:05             ` Mikko.Rapeli
2019-11-22  1:12               ` Ross Burton
2019-11-21 13:15             ` Ryan Harkin
2019-11-21 13:38               ` Nicolas Dechesne
2019-11-21 13:53                 ` Ryan Harkin
2019-11-22  0:11                   ` Andre McCurdy
2019-11-20 21:39 ` Mikko.Rapeli
2019-11-20 23:05   ` Adrian Bunk [this message]
2019-11-21  8:01     ` Mikko.Rapeli

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=20191120230555.GA3962@localhost \
    --to=bunk@stusta.de \
    --cc=Mikko.Rapeli@bmw.de \
    --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.