A new mailing list was recently introduced for documentation related
discussions including patches. And the domain for Yocto mailing lists
was changed with the migration to groups.io.
Change-Id: If687dcbaef4adf128196d8c80f3ea8b1b31b7738
Signed-off-by: Peter Kjellerstedt
---
tests/test_mbox_maili
On Wed, 2020-04-15 at 16:05 -0700, akuster wrote:
>
>
> On 4/15/20 3:25 PM, Paul Eggleton wrote:
> > Release notes draft attached, including a dedication to Scott
> > (wasn't sure where to put that so I've just left it at the top) and
> > contributors list. Let me know if you notice anything
> >
On 4/15/20 3:25 PM, Paul Eggleton wrote:
> Release notes draft attached, including a dedication to Scott (wasn't sure
> where to put that so I've just left it at the top) and contributors list. Let
> me know if you notice anything missing/incorrect.
Thanks for pulling this together.
>
> I've a
Release notes draft attached, including a dedication to Scott (wasn't sure
where to put that so I've just left it at the top) and contributors list. Let
me know if you notice anything missing/incorrect.
I've also sent out the 3.1 migration guide for the reference manual, Richard
has just merge
FYI, we’re doing the same internally (vendor supplied FIPS supported openssl
1.0.2), and the layer Armin suggests worked for us on zeus with minimal
additional tweaking.
Good luck!
-Sean
From: yocto@lists.yoctoproject.org On Behalf Of
akuster
Sent: Wednesday, April 15, 2020 9:23 AM
To: MikeB
On 4/15/20 9:16 AM, MikeB wrote:
> I'm working on a set of platforms that have a FIPs certified OpenSSL.
> We are at version 1.0.2l.
>
> I've found that the new version of python in Zeus (2.7.17) requires a
> newer version of OpenSSL (1.1).
>
> We really don't want to go through a new round of c
I think python2 *recipe* requires openssl 1.1, but python2 itself will work
just fine with openssl 1.0. So you only need to adjust the dependency,
there are several ways to do that.
Alex
On Wed, 15 Apr 2020 at 18:16, MikeB wrote:
> I'm working on a set of platforms that have a FIPs certified Op
I'm working on a set of platforms that have a FIPs certified OpenSSL. We are
at version 1.0.2l.
I've found that the new version of python in Zeus (2.7.17) requires a newer
version of OpenSSL (1.1).
We really don't want to go through a new round of certification, so we want to
keep our current
