From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <amayajindal786@gmail.com>
Cc: <alex.kanavin@gmail.com>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Issue while adding the support for TLS1.3 in existing krogoth yocto #yocto #yocto #yocto #yocto #apt #raspberrypi #yocto
Date: Tue, 18 Feb 2020 09:06:28 +0000 [thread overview]
Message-ID: <20200218090628.GC104502@korppu> (raw)
In-Reply-To: <-rwstc27cdt90-auuyo41rs8jtvzm6syoph8qyesn3ii-mwuzy2-dgobygumtd4d-75yhts2n0qmc-f0uc4f-r9fqcx4aa7a041vjua4rn8a56jf43y-as3l4g-2l39almml2bd3opuod-lges1-2ywa6z.1582012225122@email.android.com>
Hi,
On Tue, Feb 18, 2020 at 01:20:25PM +0530, amaya jindal wrote:
> Thanks for your prompt reply. But is not there any way similar to add
> support for TLS1.3 instead of moving to new yocto releases
openssl is tricky to update and requires backporting fixes for many, many recipes
to get builds passing etc. Depending on project size, it may be possible
to update only those components which you use, e.g. backport commits from
poky master or release branches like warrior. The number of backported changes
will be large. I've ported openssl 1.1.1d patches to yocto 2.5 sumo but it wasn't
pretty. A strategy with regular yocto updates is much better and forces you
to think of your dependencies and patches much harder.
Hope this helps,
-Mikko
next prev parent reply other threads:[~2020-02-19 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 7:25 Issue while adding the support for TLS1.3 in existing krogoth yocto #yocto #yocto #yocto #yocto #apt #raspberrypi #yocto amayajindal786
2020-02-18 7:43 ` [yocto] " Alexander Kanavin
2020-02-18 7:50 ` amayajindal786
2020-02-18 9:06 ` Mikko Rapeli [this message]
2020-02-19 7:39 ` amaya jindal
2020-03-18 11:00 ` amaya jindal
[not found] ` <15FD60EEC90B82B0.21252@lists.yoctoproject.org>
2020-03-19 12:44 ` amaya jindal
[not found] ` <15FDB5F5FFA2CF3D.29573@lists.yoctoproject.org>
2020-03-23 8:32 ` amaya jindal
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=20200218090628.GC104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=alex.kanavin@gmail.com \
--cc=amayajindal786@gmail.com \
--cc=yocto@lists.yoctoproject.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.