linux/poky.git, branch yocto-2.7.4

build-appliance-image: Update to warrior head revision

2020-05-27T06:34:50+00:00

(From OE-Core rev: db3ce703d03b18e8a4120969d32ff7f344f34fe9) Signed-off-by: Richard Purdie

prservice.py: fix do_package with newer Python in Ubuntu 20.04

2020-05-27T06:34:34+00:00

* with Ubuntu 20.04 which is using python 3.8 I'm seeing a lot of errors like: ERROR: libxml2-2.9.10-r0 do_package: Can NOT get PRAUTO, exception No module named '_sysconfigdata' not sure what caused this from python 3.8, but this seems to work * PRserv is enabled with: PRSERV_HOST = "localhost:0" (From OE-Core rev: 4b26eaf7152fb712aba47a0c746333578f58ee8d) (From OE-Core rev: eaa6de34442906ad6285aa069f17a7cb2a64e970) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

build-appliance-image: Update to warrior head revision

2020-05-26T22:17:14+00:00

(From OE-Core rev: bcd9ae6fbb2258787bdea260fed5663791353f5a) Signed-off-by: Richard Purdie

poky.conf: Bump version for 2.7.4 warrior release

2020-05-26T22:17:05+00:00

(From meta-yocto rev: e16269fae87b674a686c96488daa2120f0ea8ba7) Signed-off-by: Richard Purdie

cve-check: CPE version '-' as all version

2020-05-22T15:23:30+00:00

CPE version could be '-' to mean no version info. Current cve_check treat it as not valid and does not report these CVE but some of these could be a valid vulnerabilities. Since non-valid CVE can be whitelisted, so treat '-' as all version and report all these CVE to capture possible vulnerabilities. Non-valid CVE to be whitelisted separately. [YOCTO #13617] (From OE-Core rev: 1d06fedf46c8f67fccde7a00d7199d7052c33b30) Signed-off-by: Lee Chee Yang Signed-off-by: Richard Purdie (cherry picked from commit c69ee3594079589d27c10db32bc288566ebde9ef) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

openssl: upgrade 1.1.1f -> 1.1.1g

2020-05-22T15:23:30+00:00

This also fixes CVE-2020-1967. (From OE-Core rev: 620d69e7ad0d0c40ecd135e48f96aaf368c7f242) Signed-off-by: Jan Luebbe Signed-off-by: Anuj Mittal Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

openssl: update to 1.1.1f

2020-05-22T15:23:30+00:00

This also un-breaks python3 ptest which got broken with 1.1.1e update. (From OE-Core rev: c74958fe05db584289ee560584190b3a0b25155d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit b4ddf5b9d8cd769b7026663f93c8bc69b55d8cbf) [AK: bugfix only update] Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

openssl: Upgrade 1.1.1d -> 1.1.1e

2020-05-22T15:23:30+00:00

Backported patch removed. (From OE-Core rev: 4dc340d63d29e632c8402342cf4b66a41c9c5f93) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie (cherry picked from commit 710bc0f8544f54750c8fb7b8affa243932927a24) [AK: bug fix only update] Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

openssl: recommend cryptodev-module for corresponding PACKAGECONFIG

2020-05-22T15:23:29+00:00

(From OE-Core rev: 5de53272951bfc3c8c73bd09fd0b296e2ffff322) Signed-off-by: Denys Dmytriyenko Signed-off-by: Richard Purdie (cherry picked from commit 57fcf9b517fe95e871122946cb99fe7fa9fd2e26) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

openssl: Fix reproducibility issue

2020-05-22T15:23:29+00:00

There was a build architecture leaking into the target ptest which could vary depending upon host. Remove it as its cosmetic. [YOCTO #13770] (From OE-Core rev: 37db519eedb7eb5cd4f14d05f30f5d580aa7458d) (From OE-Core rev: c31c676319812e6fc036741db2ab8e16eccff723) (From OE-Core rev: 4a8d927dc3ef569830c417d46e5d0a0318a69cde) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie