From: akuster808 <akuster808@gmail.com>
To: robert_joslyn@selinc.com, openembedded-core@lists.openembedded.org
Subject: Re: Backport OpenSSL 1.0.2n
Date: Tue, 13 Feb 2018 08:27:52 -0800 [thread overview]
Message-ID: <00ccda06-5caf-0aad-9df8-df46a8b40a9f@gmail.com> (raw)
In-Reply-To: <OFDC897003.15BD668A-ON88258232.006ED4D2-88258232.00742260@selinc.com>
On 02/12/2018 01:08 PM, robert_joslyn@selinc.com wrote:
> I'm working with the pyro release, and noticed that it's still using
> openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n, which is
> already available on master. Is there a reason that the newer version
> hasn't made it back to pyro (or rocko, which is on 1.0.2m)?
openssl 1.1 was added and the openssl files got restructured making
simple cherry-picking not an option for older releases.
1.0.2n hit master 7 days ago, sorry for the delay.
1.0.2n is now in stable/rocko-next and will migrate to rocko when
appropriate.
> I know new
> package versions are not normally backported, but looking at the change
> log, I only see one change mentioned that is not a CVE fix (the 1.0.2l
> release):
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git.openssl.org_-3Fp-3Dopenssl.git-3Ba-3Dblob-3Bf-3DCHANGES-3Bh-3Df2fc31a25c54b12fc7db40c03d39f9a68b9ec0e5-3Bhb-3De5bba24cd8bb3e5127a578b85c6edf013a38ea6d&d=DwIBAg&c=zVFQZQ67ypsA9mYKSCqWmQHiVkCCaN-Gb60_N6TVnLk&r=ak_pMnzuMKndrbvJGok-seoFenjTGhP3oPNUzKUOwzHhGpNMwSJsaHunyXDlBGjO&m=3JjPoO2FeIBSz3wggiqKGtYceKB5t__oSe8p6yDsQfM&s=oeCHfmZkkXVFW1aoMZsolXeFvKI9RTUtbdGBj61kheQ&e=
>
> I can send patches to bring 1.0.2n to rocko and pyro if they will be
> accepted.
patches welcome
- Armin
>
> Thanks,
> Robert
next prev parent reply other threads:[~2018-02-13 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 21:08 Backport OpenSSL 1.0.2n robert_joslyn
2018-02-13 7:02 ` Alexander Kanavin
2018-02-13 16:27 ` akuster808 [this message]
2018-02-13 19:53 ` robert_joslyn
2018-02-14 15:58 ` Richard Purdie
2018-02-14 17:26 ` 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=00ccda06-5caf-0aad-9df8-df46a8b40a9f@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=robert_joslyn@selinc.com \
/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