Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][RFC][PATCH] Remove openssl10
Date: Fri, 26 Apr 2019 08:12:15 +0300	[thread overview]
Message-ID: <20190426051215.GA26023@localhost> (raw)
In-Reply-To: <bf9d998e-487b-32a0-7879-9f0694a835ee@windriver.com>

On Thu, Apr 25, 2019 at 03:18:47PM -0500, Mark Hatle wrote:
> On 4/25/19 2:28 PM, Adrian Bunk wrote:
> > Would you consider this patch appropriate now that warrior has branched?
> 
> The use of OpenSSL10 as a 'second library' is likely no longer needed.  But
> OpenSSL 1.0 (as an alternative version) to OpenSSL 1.1 is still needed in some
> cases.. (FIPS-140-2)

Is anyone actually security-maintaining OpenSSL in OE?

The just released sumo has both versions of OpenSSL not touched since 
August, despite just upgrading to the latest versions would fix CVEs.

> So removal of openssl10 is fine, but if there are patches for support of both
> versions (old/new) of OpenSSL they will be needed at least through the end of
> this year for many users.

This is now for Yocto 2.8, which will be released October/November
this year.

> --Mark

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-04-26  5:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 18:49 [meta-oe][RFC][PATCH] Remove openssl10 Adrian Bunk
2019-03-08 19:15 ` Alexander Kanavin
2019-03-08 19:38   ` Adrian Bunk
2019-03-08 20:21     ` Alexander Kanavin
2019-03-08 20:39       ` Adrian Bunk
2019-04-25 19:28         ` Adrian Bunk
2019-04-25 20:18           ` Mark Hatle
2019-04-26  5:12             ` Adrian Bunk [this message]
2019-04-26 15:31               ` Mark Hatle
2019-04-26 15:50                 ` Adrian Bunk
2019-04-26 17:56                   ` Mark Hatle
2019-04-29 11:39                     ` Alexander Kanavin
2019-03-09 21:30     ` akuster808

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=20190426051215.GA26023@localhost \
    --to=bunk@stusta.de \
    --cc=mark.hatle@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox