|
Re: [isar-cip-core][PATCH v2] swupdate-config: add prefix to variables
SWUPDATE_U_BOOT should be the name of the u-boot package.
In case the layer (e.g. isar-cip-core) supplies the u-boot binary, `SWUPDATE_U_BOOT` should be defined as `u-boot-${MACHINE}`.
Debian
SWUPDATE_U_BOOT should be the name of the u-boot package.
In case the layer (e.g. isar-cip-core) supplies the u-boot binary, `SWUPDATE_U_BOOT` should be defined as `u-boot-${MACHINE}`.
Debian
|
By
Quirin Gylstorff
·
#6413
·
|
|
Re: [isar-cip-core][PATCH v2] README.secureboot: Corrections
Thanks, applied.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
Thanks, applied.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
|
By
Jan Kiszka
·
#6412
·
|
|
Re: [isar-cip-core][PATCH v2] swupdate-config: add prefix to variables
Still leaves me and probably other users clueless what SWUPDATE_U_BOOT
should be. Simply "u-boot-${MACHINE}"?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
Still leaves me and probably other users clueless what SWUPDATE_U_BOOT
should be. Simply "u-boot-${MACHINE}"?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
|
By
Jan Kiszka
·
#6411
·
|
|
Re: [isar-cip-core][RFC] Add option to use swupdate-handler-roundrobin
...but the in-tree handler does. How much effort is needed to port that
feature into the new handler?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
...but the in-tree handler does. How much effort is needed to port that
feature into the new handler?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
|
By
Jan Kiszka
·
#6410
·
|
|
Re: [isar-cip-core][PATCH v2] README.secureboot: Corrections
Do you want to mention qemu-system-x86_64 --version should be 5.2.0 or higher as default Debian buster has older version of qemu and this step fails with older version.
Also these steps can't be
Do you want to mention qemu-system-x86_64 --version should be 5.2.0 or higher as default Debian buster has older version of qemu and this step fails with older version.
Also these steps can't be
|
By
Dinesh Kumar
·
#6409
·
|
|
[isar-cip-core][RFC] Add option to use swupdate-handler-roundrobin
From: Quirin Gylstorff <quirin.gylstorff@...>
The new swupdate round robin handler is available under[1].
Add the Option `SWUPDATE_USE_ROUND_ROBIN_HANDLER_REPO` to
use the handler directly
From: Quirin Gylstorff <quirin.gylstorff@...>
The new swupdate round robin handler is available under[1].
Add the Option `SWUPDATE_USE_ROUND_ROBIN_HANDLER_REPO` to
use the handler directly
|
By
Quirin Gylstorff
·
#6408
·
|
|
[isar-cip-core][PATCH v2] README.secureboot: Corrections
From: Quirin Gylstorff <quirin.gylstorff@...>
- Add code block for key insertion for better visibility
- Correct the template for user-generated keys
- Add information where to store the
From: Quirin Gylstorff <quirin.gylstorff@...>
- Add code block for key insertion for better visibility
- Correct the template for user-generated keys
- Add information where to store the
|
By
Quirin Gylstorff
·
#6407
·
|
|
[isar-cip-core][PATCH v2] swupdate-config: add prefix to variables
From: Quirin Gylstorff <quirin.gylstorff@...>
The variables U_BOOT and BOOTLOADER are only used for swupdate.
Add the prefix SWUPDATE to indicate the intended usage.
Signed-off-by: Quirin
From: Quirin Gylstorff <quirin.gylstorff@...>
The variables U_BOOT and BOOTLOADER are only used for swupdate.
Add the prefix SWUPDATE to indicate the intended usage.
Signed-off-by: Quirin
|
By
Quirin Gylstorff
·
#6406
·
|
|
Re: [isar-cip-core][PATCH] swupdate-config: add prefix to variables
Does not fully parse to me. Do you mean
"The variables U_BOOT and BOOTLOADER are only used for swupdate.
Add the prefix SWUPDATE to indicate the intended usage."
?
This doesn't make sense. There is
Does not fully parse to me. Do you mean
"The variables U_BOOT and BOOTLOADER are only used for swupdate.
Add the prefix SWUPDATE to indicate the intended usage."
?
This doesn't make sense. There is
|
By
Jan Kiszka
·
#6405
·
|
|
Re: [isar-cip-core][PATCH] README.secureboot: Corrections
These two look spurious.
Unneded new-line?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
These two look spurious.
Unneded new-line?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
|
By
Jan Kiszka
·
#6404
·
|
|
[isar-cip-core][PATCH] README.secureboot: Corrections
From: Quirin Gylstorff <quirin.gylstorff@...>
- Add code block for key insertion for better visibility
- Correct the template for user-generated keys
- Add information where to store the
From: Quirin Gylstorff <quirin.gylstorff@...>
- Add code block for key insertion for better visibility
- Correct the template for user-generated keys
- Add information where to store the
|
By
Quirin Gylstorff
·
#6403
·
|
|
[isar-cip-core][PATCH] swupdate-config: add prefix to variables
From: Quirin Gylstorff <quirin.gylstorff@...>
The variables U_BOOT and BOOTLOADER are only used for swupdate
mark add the prefix SWUPDATE to indicate the intended usage.
Signed-off-by:
From: Quirin Gylstorff <quirin.gylstorff@...>
The variables U_BOOT and BOOTLOADER are only used for swupdate
mark add the prefix SWUPDATE to indicate the intended usage.
Signed-off-by:
|
By
Quirin Gylstorff
·
#6402
·
|
|
Re: [PATCH 2/2] [isar-cip-core] Add support qemu-arm
It looks to me we have some regressions in master (which does
deployment), caused by these commits. Could you have a look
It looks to me we have some regressions in master (which does
deployment), caused by these commits. Could you have a look
|
By
Jan Kiszka
·
#6401
·
|
|
Cip-kernel-sec Updates for Week of 2021-04-29
Hi everyone,
This was a quiet week. Only one new issue:
- CVE-2021-3501 [x86: KVM: VMX: data race condition] - fixed
Nothing else to report on.
Regards
ChenYu
Hi everyone,
This was a quiet week. Only one new issue:
- CVE-2021-3501 [x86: KVM: VMX: data race condition] - fixed
Nothing else to report on.
Regards
ChenYu
|
By
Chen-Yu Tsai (Moxa) <wens@...>
·
#6400
·
|
|
NO IRC meeting today
Hi, All,
As was discussed last week, there is no IRC meeting today.
See you next week.
Best regards,
--
M. Kudo
Hi, All,
As was discussed last week, there is no IRC meeting today.
See you next week.
Best regards,
--
M. Kudo
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#6399
·
|
|
Re: [Inquiry for CVE-2021-23133] -- necessity of the backporting
Hi, Jan-san,
Thanks for your feedback.
Iwamatsu-san,
Thanks for sharing the latest status.
So, let me drop this request.
Best regards,
--
M. Kudo
Hi, Jan-san,
Thanks for your feedback.
Iwamatsu-san,
Thanks for sharing the latest status.
So, let me drop this request.
Best regards,
--
M. Kudo
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#6398
·
|
|
Re: [Inquiry for CVE-2021-23133] -- necessity of the backporting
Hi,
By
Nobuhiro Iwamatsu
·
#6397
·
|
|
Re: [Inquiry for CVE-2021-23133] -- necessity of the backporting
I can try to listen around, but I see way more users (based on configs) than
I can try to listen around, but I see way more users (based on configs) than
|
By
Jan Kiszka
·
#6396
·
|
|
Failing -stable-rc testing
Hi!
This happened several times now:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/1211168409
Waiting for pod gitlab/runner-z9bugs8s-project-14394223-concurrent-9kltbz to be
Hi!
This happened several times now:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/1211168409
Waiting for pod gitlab/runner-z9bugs8s-project-14394223-concurrent-9kltbz to be
|
By
Pavel Machek
·
#6395
·
|
|
[Inquiry for CVE-2021-23133] -- necessity of the backporting
Hi, Jan-san, Minda-san,
https://lists.cip-project.org/g/cip-dev/message/6382
As was reported by Chen-Yu san last week, the following CVE security patch is not yet backported to kernels before
Hi, Jan-san, Minda-san,
https://lists.cip-project.org/g/cip-dev/message/6382
As was reported by Chen-Yu san last week, the following CVE security patch is not yet backported to kernels before
|
By
masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
·
#6394
·
|