Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-12 Thread Andre McCurdy
On Tue, Aug 28, 2018 at 3:23 AM, Alexander Kanavin wrote: > From: Alexander Kanavin > > I believe the time has come to do this: openssl 1.0 upstream support stops at > the end > of 2019, and we do not want a situation where a supported YP release contains > an > unsupported version of a

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-10 Thread Khem Raj
we are good with fixes in master-next On Mon, Sep 10, 2018 at 10:54 AM Andre McCurdy wrote: > > On Wed, Sep 5, 2018 at 8:55 AM, Martin Jansa wrote: > > https://wiki.debian.org/OpenSSL-1.1 says it will cause runtime bugs like > > segmentation faults or just misbehaving applications. > > > > On

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-10 Thread Andre McCurdy
On Wed, Sep 5, 2018 at 8:55 AM, Martin Jansa wrote: > https://wiki.debian.org/OpenSSL-1.1 says it will cause runtime bugs like > segmentation faults or just misbehaving applications. > > On Wed, Sep 5, 2018 at 5:45 PM Andre McCurdy wrote: >> >> On Wed, Sep 5, 2018 at 8:15 AM, Khem Raj wrote: >>

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Martin Jansa
https://wiki.debian.org/OpenSSL-1.1 says it will cause runtime bugs like segmentation faults or just misbehaving applications. On Wed, Sep 5, 2018 at 5:45 PM Andre McCurdy wrote: > On Wed, Sep 5, 2018 at 8:15 AM, Khem Raj wrote: > > On Wed, Sep 5, 2018 at 7:45 AM Richard Purdie > > wrote: >

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Andre McCurdy
On Wed, Sep 5, 2018 at 8:15 AM, Khem Raj wrote: > On Wed, Sep 5, 2018 at 7:45 AM Richard Purdie > wrote: >> >> On Wed, 2018-09-05 at 10:53 +0200, Martin Jansa wrote: >> > But patching the components to use libssl10 might actually work >> > (unlike >> > just changing DEPENDS to openssl10). >> >

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Khem Raj
On Wed, Sep 5, 2018 at 7:45 AM Richard Purdie wrote: > > On Wed, 2018-09-05 at 10:53 +0200, Martin Jansa wrote: > > But patching the components to use libssl10 might actually work > > (unlike > > just changing DEPENDS to openssl10). > > > > It's not only conflicting in build-time in RSS, but it

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Richard Purdie
On Wed, 2018-09-05 at 10:53 +0200, Martin Jansa wrote: > But patching the components to use libssl10 might actually work > (unlike > just changing DEPENDS to openssl10). > > It's not only conflicting in build-time in RSS, but it will conflict > on target as well. You either need to migrate all

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Martin Jansa
On Wed, Sep 05, 2018 at 09:14:21AM +0200, Alexander Kanavin wrote: > I am also disappointed to see that openssl10 does not help much, > however, I do not believe we should wait another year, and hope the > problem would take care of itself - this clearly did not happen over > the past year. Let's

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-05 Thread Alexander Kanavin
I am also disappointed to see that openssl10 does not help much, however, I do not believe we should wait another year, and hope the problem would take care of itself - this clearly did not happen over the past year. Let's just look at failing recipes one by one and investigate what needs to be

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Khem Raj
On Tue, Sep 4, 2018 at 9:08 PM Andre McCurdy wrote: > > On Tue, Sep 4, 2018 at 6:49 PM, Khem Raj wrote: > > On Tue, Sep 4, 2018 at 3:58 PM wrote: > >> > >> On Tue, 2018-09-04 at 13:43 -0700, Khem Raj wrote: > >> > I pointed this earlier before merge as well > >> > meta-openembedded has 40 odd

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Andre McCurdy
On Tue, Sep 4, 2018 at 6:49 PM, Khem Raj wrote: > On Tue, Sep 4, 2018 at 3:58 PM wrote: >> >> On Tue, 2018-09-04 at 13:43 -0700, Khem Raj wrote: >> > I pointed this earlier before merge as well >> > meta-openembedded has 40 odd recipes failing due to openssl 1.1 >> > upgrade >> >> Sorry, I think

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Khem Raj
On Tue, Sep 4, 2018 at 3:58 PM wrote: > > On Tue, 2018-09-04 at 13:43 -0700, Khem Raj wrote: > > I pointed this earlier before merge as well > > meta-openembedded has 40 odd recipes failing due to openssl 1.1 > > upgrade > > Sorry, I think I missed something somewhere as I thought the >

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread richard . purdie
On Tue, 2018-09-04 at 13:43 -0700, Khem Raj wrote: > I pointed this earlier before merge as well > meta-openembedded has 40 odd recipes failing due to openssl 1.1 > upgrade Sorry, I think I missed something somewhere as I thought the indications were the bigger problems like qt5 were working now

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Khem Raj
On Tue, Sep 4, 2018 at 1:35 PM Richard Purdie wrote: > > On Tue, 2018-09-04 at 21:12 +0200, Martin Jansa wrote: > > On Tue, Aug 28, 2018 at 12:23 PM Alexander Kanavin > l.com> wrote: > > > From: Alexander Kanavin > > > > > > I believe the time has come to do this: openssl 1.0 upstream > > >

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Richard Purdie
On Tue, 2018-09-04 at 21:12 +0200, Martin Jansa wrote: > On Tue, Aug 28, 2018 at 12:23 PM Alexander Kanavin l.com> wrote: > > From: Alexander Kanavin > > > > I believe the time has come to do this: openssl 1.0 upstream > > support stops at the end > > of 2019, and we do not want a situation

Re: [OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-09-04 Thread Martin Jansa
On Tue, Aug 28, 2018 at 12:23 PM Alexander Kanavin wrote: > From: Alexander Kanavin > > I believe the time has come to do this: openssl 1.0 upstream support stops > at the end > of 2019, and we do not want a situation where a supported YP release > contains an > unsupported version of a

[OE-core] [RFC PATCH 1/6] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version

2018-08-28 Thread Alexander Kanavin
From: Alexander Kanavin I believe the time has come to do this: openssl 1.0 upstream support stops at the end of 2019, and we do not want a situation where a supported YP release contains an unsupported version of a critical security component. Openssl 1.0 can still be utilized by depending on