Re: [OE-core] [yocto-security] [PATCH] openssl: drop support for deprecated algorithms

2020-12-21 Thread Mark Hatle
On 12/19/20 12:04 PM, Konrad Weihmann wrote: > > > On 19.12.20 18:58, Richard Purdie wrote: >> On Sat, 2020-12-19 at 18:53 +0100, Konrad Weihmann wrote: >>> On 19.12.20 18:36, Richard Purdie wrote: PACKAGECONFIG[cryptodev-linux] =

Re: [OE-core] [yocto-security] [PATCH] openssl: drop support for deprecated algorithms

2020-12-21 Thread Andre McCurdy
On Sat, Dec 19, 2020 at 4:08 PM Richard Purdie wrote: > > On Sat, 2020-12-19 at 19:04 +0100, Konrad Weihmann wrote: > > > > On 19.12.20 18:58, Richard Purdie wrote: > > > On Sat, 2020-12-19 at 18:53 +0100, Konrad Weihmann wrote: > > > > On 19.12.20 18:36, Richard Purdie wrote: > > > > >

Re: [OE-core] Process for backports

2020-12-21 Thread Peter Kjellerstedt
> -Original Message- > From: Richard Purdie > Sent: den 21 december 2020 15:10 > To: Peter Kjellerstedt ; OE Core > (openembedded-core@lists.openembedded.org) c...@lists.openembedded.org> > Cc: Anuj Mittal ; Steve Sakoman > > Subject: Re: [OE-core] Process for backports > > On Mon,

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2020-12-21 Thread Stephen Jolley
All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

[OE-core] [dunfell][PATCH 2/2] linux-firmware: package firmware for Lontium lt9611uxc bridge

2020-12-21 Thread Dmitry Baryshkov
Package firmware for Lontium lt9611uxc DSI to HDMI bridge, found e.g. on Qualcomm RB5 platform. Signed-off-by: Dmitry Baryshkov Signed-off-by: Richard Purdie (cherry picked from commit 4d16922943ffa6003d611c367b934d199c549c4c) --- .../linux-firmware/linux-firmware_20201218.bb | 10

[OE-core] [dunfell][PATCH 1/2] linux-firmware: upgrade 20201118 -> 20201218

2020-12-21 Thread Dmitry Baryshkov
License-Update: firmware versions/filenames Signed-off-by: Dmitry Baryshkov Signed-off-by: Richard Purdie (cherry picked from commit c88129ffef320c16722f40426b0d4560274dca4e) --- ...{linux-firmware_20201118.bb => linux-firmware_20201218.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [OE-core] [PATCH 0/4] pulseaudio: Autotools to Meson

2020-12-21 Thread Andrey Zhizhikin
Hello Tanu, On Sun, Dec 20, 2020 at 5:09 PM Khem Raj wrote: > > On Sun, Dec 20, 2020 at 6:26 AM Tanu Kaskinen wrote: > > > > On Sat, 2020-12-19 at 12:36 -0800, Khem Raj wrote: > > > On Sat, Dec 19, 2020 at 9:24 AM Khem Raj wrote: > > > > On Thu, Dec 17, 2020 at 11:28 AM Tanu Kaskinen wrote: >

[OE-core] Process for backports

2020-12-21 Thread Peter Kjellerstedt
I thought the process for backporting changes in OE-Core was: master -> gatesgarth -> dunfell -> ... However, I just noticed that the latest Gatesgarth release (24.0.1) is still at 2020b of timezone, whereas Dunfell (23.0.4) has 2020d. Am I missing something here, or is this just a miss in

Re: [OE-core][dunfell 00/28] Patch review - pseudo file mode corruption fix series

2020-12-21 Thread Steve Sakoman
On Mon, Dec 21, 2020 at 4:33 AM Martin Jansa wrote: > > Just curious, is this PR on hold or rejected completely? > > I don't have strong opinion either way, I was just wondering about this one > when other newer PRs were already merged. This series is still actively being tested. I've been

Re: [OE-core] [PATCH 0/4] pulseaudio: Autotools to Meson

2020-12-21 Thread Andrey Zhizhikin
Hello Tanu, On Mon, Dec 21, 2020 at 2:25 PM Tanu Kaskinen wrote: > > On Mon, 2020-12-21 at 14:03 +0100, Andrey Zhizhikin wrote: > > Hello Tanu, > > > > On Sun, Dec 20, 2020 at 5:09 PM Khem Raj wrote: > > > On Sun, Dec 20, 2020 at 6:26 AM Tanu Kaskinen wrote: > > > > On Sat, 2020-12-19 at 12:36

Re: [OE-core] Process for backports

2020-12-21 Thread Richard Purdie
On Mon, 2020-12-21 at 13:30 +, Peter Kjellerstedt wrote: > I thought the process for backporting changes in OE-Core was: > > master -> gatesgarth -> dunfell -> ... > > However, I just noticed that the latest Gatesgarth release (24.0.1) > is still at 2020b of timezone, whereas Dunfell

Re: [OE-core][dunfell 00/28] Patch review - pseudo file mode corruption fix series

2020-12-21 Thread Martin Jansa
Just curious, is this PR on hold or rejected completely? I don't have strong opinion either way, I was just wondering about this one when other newer PRs were already merged. On Thu, Dec 3, 2020 at 4:08 PM Steve Sakoman wrote: > Issues with undetected file mode corruption in pseudo have been

Re: [OE-core] [PATCH 0/4] pulseaudio: Autotools to Meson

2020-12-21 Thread Tanu Kaskinen
On Mon, 2020-12-21 at 14:03 +0100, Andrey Zhizhikin wrote: > Hello Tanu, > > On Sun, Dec 20, 2020 at 5:09 PM Khem Raj wrote: > > On Sun, Dec 20, 2020 at 6:26 AM Tanu Kaskinen wrote: > > > On Sat, 2020-12-19 at 12:36 -0800, Khem Raj wrote: > > > > On Sat, Dec 19, 2020 at 9:24 AM Khem Raj wrote:

Re: [OE-core] [PATCH] pulseaudio: Fix build with clang for non-x86 target

2020-12-21 Thread Tanu Kaskinen
On Sun, 2020-12-20 at 08:05 -0800, Khem Raj wrote: > Signed-off-by: Khem Raj > Cc: Tanu Kaskinen > --- > .../0001-meson-Check-for-__get_cpuid.patch| 82 +++ > .../pulseaudio/pulseaudio_14.0.bb | 1 + > 2 files changed, 83 insertions(+) > create mode 100644 >

[OE-core] [PATCH] pulseaudio: fix client.conf location

2020-12-21 Thread Tanu Kaskinen
The location of the generated client.conf changed when switching from Autotools to Meson. Fixes this error when enabling autospawn-for-root: sed: can't read src/client.conf: No such file or directory Signed-off-by: Tanu Kaskinen --- meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 2 +-

[OE-core] [PATCH] cups: Mark CVE-2008-1033 as a non-issue

2020-12-21 Thread Richard Purdie
It only applies to MacOS. Signed-off-by: Richard Purdie --- meta/recipes-extended/cups/cups.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-extended/cups/cups.inc b/meta/recipes-extended/cups/cups.inc index 91e73d75e43..e7a704134c6 100644 ---

Re: [OE-core] [yocto-security] OE-core CVE metrics for master on Sun 20 Dec 2020 07:15:01 AM HST

2020-12-21 Thread Richard Purdie
On Sun, 2020-12-20 at 07:24 -1000, Steve Sakoman wrote: Branch: master > CVE-2007-3387: cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-3387 * CVE-2007-4045: cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4045 * > CVE-2008-1033: cups

[OE-core] [PATCH] apr-util: Only specify --with-dbm=gdbm if gdbm support is enabled

2020-12-21 Thread Peter Kjellerstedt
Support for gdbm was made optional in 3260ad9e, but it was still being used unconditionally. Signed-off-by: Peter Kjellerstedt --- meta/recipes-support/apr/apr-util_1.6.1.bb | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/meta/recipes-support/apr/apr-util_1.6.1.bb

Re: [OE-core] [PATCH 1/2] sysvinit/rc: show text progress

2020-12-21 Thread Trevor Woerner
Oops, there is no 2/2, this is a singular patch. Should I resend? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#146036): https://lists.openembedded.org/g/openembedded-core/message/146036 Mute This Topic:

[OE-core] [PATCH 1/2] sysvinit/rc: show text progress

2020-12-21 Thread Trevor Woerner
In addition to the progress bar, show which startup routine is running by using the "MSG" facility of psplash. Signed-off-by: Trevor Woerner --- meta/recipes-core/sysvinit/sysvinit/rc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/sysvinit/sysvinit/rc

[OE-core] [PATCH] run-postinsts: fix setting pi_dir

2020-12-21 Thread Trevor Woerner
The pi_dir variable isn't being set properly; it gets set to the value of the *previous* package manager. Given the order of "rpm deb ipk", if the script determines that the package manager is "ipk", pi_dir remains set at SYSCONFDIR/deb-postinsts. Signed-off-by: Trevor Woerner ---

Re: [OE-core] [PATCH] groff: Fix reproducibility issue

2020-12-21 Thread Steve Sakoman
On Mon, Dec 21, 2020 at 7:32 AM Richard Purdie wrote: > > groff chooses a default papersize depending on the value from /etc/papersize > and failing that, the search domain in /etc/resolv.conf based on the comment > in configure: > > """ > If the top-level domain is two letters and it's not 'us'

[OE-core] [PATCH] groff: Fix reproducibility issue

2020-12-21 Thread Richard Purdie
groff chooses a default papersize depending on the value from /etc/papersize and failing that, the search domain in /etc/resolv.conf based on the comment in configure: """ """ Oddly, my system sets to "a4" in /etc/papersize which means it defaults to "letter" since its != "A4". These defaults

[OE-core] [PATCH] groff: Fix reproducibility issue

2020-12-21 Thread Richard Purdie
groff chooses a default papersize depending on the value from /etc/papersize and failing that, the search domain in /etc/resolv.conf based on the comment in configure: """ If the top-level domain is two letters and it's not 'us' or 'ca' then they probably use A4 paper. """ Oddly, my system sets

Re: [OE-core] How to set the password Hashing Algorithm for root user to SHA256 or SHA512

2020-12-21 Thread Sourabh Banerjee
On 2020-12-20 10:16, Khem Raj wrote: On Sat, Dec 19, 2020 at 11:58 AM Sourabh Banerjee wrote: [Edited Message Follows] The image I generated seems to use MD5 for root password hashing. I understood this from the /etc/shadow file in the image., the file has following line: