All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/26] thud patch review
Date: Tue, 19 Mar 2019 14:55:38 +0100	[thread overview]
Message-ID: <20190319135538.GH1994@jama> (raw)
In-Reply-To: <22BB06E0-D9DD-4070-960B-53D03755B65A@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

On Tue, Mar 19, 2019 at 12:35:59PM +0100, Alexander Kanavin wrote:
> Just to remind once more, all upstream support for OpenSSL 1.0.2 ceases in 9 months, so shipping products with it may not be the best idea.

Just to remind once more, shipping products isn't as easy as building
the few recipes included in oe-core.

For example:
Believe it or not, some projects need to use old Qt 5.6 due to license
change in newer version and 5.6 doesn't support openssl 1.1,
backporting the necessary changes would violate the license as well.
Providing clean room re-implementation is also difficult, because there
aren't many other options how to implement this than how it was done in
newer qt already, see:

https://bugreports.qt.io/browse/QTBUG-71623
https://development.qt-project.narkive.com/RW4wxYXY/openssl-1-1-x-support-on-qt-5-6-5-9

Yes, it's not the best idea, but even backporting security fixes to old
openssl might be cheaper than buying commercial qt license...

Cheeers,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2019-03-19 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  2:36 [PATCH 00/26] thud patch review Armin Kuster
2019-03-19  8:55 ` Martin Jansa
2019-03-19 10:22   ` Alexander Kanavin
2019-03-19 10:40     ` Martin Jansa
2019-03-19 11:35       ` Alexander Kanavin
2019-03-19 13:55         ` Martin Jansa [this message]
2019-03-19 16:31           ` Alexander Kanavin
2019-03-19 17:07             ` Martin Jansa
2019-03-19 14:52   ` akuster808
2019-03-19 15:40     ` Alexander Kanavin
2019-03-19  9:05 ` Vincent Prince

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=20190319135538.GH1994@jama \
    --to=martin.jansa@gmail.com \
    --cc=alex.kanavin@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.