2023-09-18 10:05:18 |
Aristo Chen |
bug |
|
|
added bug |
2023-09-19 01:41:03 |
Aristo Chen |
description |
Subject: backport mkeficapsule to jammy
[Impact]
* mkeficapsule command is used to generate capsule file for updating firmware in u-boot
[Test case]
Test case 1:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
2. try to update the capsule file(both test_new.cap and test_old.cap)
3. check if the U-Boot build stamp is different from previous
Test case 2:
1. Follow the command(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) here to test with U-Boot sandbox, and the test_efi_capsule related files were skipped by default before or ater the code changes, the test result can be found in comment
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, so the regression risk should be low
[Other Info]
N/A |
[Impact]
* mkeficapsule command is used to generate capsule file for updating firmware in u-boot
[Test case]
Test case 1:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
2. try to update the capsule file(both test_new.cap and test_old.cap)
3. check if the U-Boot build stamp is different from previous
Test case 2:
1. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, and the test_efi_capsule related files were skipped by default before or ater the code changes, the test result can be found in comment
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, so the regression risk should be low
[Other Info]
N/A |
|
2023-09-19 02:03:30 |
Aristo Chen |
attachment added |
|
jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5701855/+files/jammy.debdiff |
|
2023-09-19 02:04:31 |
Aristo Chen |
attachment added |
|
mkeficapsule.log https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5701856/+files/mkeficapsule.log |
|
2023-09-19 07:42:21 |
Aristo Chen |
tags |
|
oem-priority originate-from-2031356 |
|
2023-09-19 07:43:27 |
Aristo Chen |
bug task added |
|
oem-priority |
|
2023-09-19 07:43:47 |
Aristo Chen |
oem-priority: assignee |
|
Aristo Chen (aristochen) |
|
2023-09-19 07:43:53 |
Aristo Chen |
oem-priority: importance |
Undecided |
High |
|
2023-09-19 07:43:57 |
Aristo Chen |
oem-priority: status |
New |
Confirmed |
|
2023-09-19 08:17:08 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority originate-from-2031356 |
oem-priority originate-from-2031356 patch |
|
2023-09-19 08:17:12 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors |
2023-09-19 08:31:10 |
Aristo Chen |
attachment added |
|
mkeficapsule_sudo.log https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5701942/+files/mkeficapsule_sudo.log |
|
2023-09-19 08:33:17 |
Aristo Chen |
attachment added |
|
jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5701943/+files/jammy.debdiff |
|
2023-09-19 08:38:39 |
Aristo Chen |
attachment removed |
jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5701855/+files/jammy.debdiff |
|
|
2023-09-20 02:25:48 |
Aristo Chen |
description |
[Impact]
* mkeficapsule command is used to generate capsule file for updating firmware in u-boot
[Test case]
Test case 1:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
2. try to update the capsule file(both test_new.cap and test_old.cap)
3. check if the U-Boot build stamp is different from previous
Test case 2:
1. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, and the test_efi_capsule related files were skipped by default before or ater the code changes, the test result can be found in comment
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, so the regression risk should be low
[Other Info]
N/A |
[Impact]
* mkeficapsule is a standalone command used to generate capsule file for updating firmware in u-boot
* mkeficapsule code exists in Jammy already, but not shipped in u-boot-tools debian package, so users are not able to generate capsule file in Jammy environment, and since the mkeficapsule command is not available in Jammy, ideally no one should be impacted.
[Test case]
Test case 1:
Users can use mkeficapsule to generate capsule file which contains firmware, or anything they want, such as dtb or fip.bin, we use mkeficapsule to create a capsule file that contains U-Boot in this test case
prerequisite:
1. Please prepare a device that is capable to use capsule file to update firmware
2. Prepare your own key by this command
$ openssl req -x509 -sha256 -newkey rsa:2048 -subj /CN=TEST_SIGNER/ -keyout SIGNER.key -out SIGNER.crt -nodes -days 365
steps:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
$ mkeficapsule --private-key SIGNER.key --certificate SIGNER.crt --monotonic-count 1 --instance 0 --index 2 --guid "12345678-abcd-1234-5678-12345678abcd" test.bin test_new.cap
2. Put the capsule file to required path(both test_new.cap and test_old.cap)
3. Reboot device and stop at u-boot prompt, then type the command. Note the actual location of test_new.cap may bedifferent in your case
=> efidebug boot add -b 0 0 mmc 0:8 test_new.cap
4. The device should reset and check if the U-Boot build stamp is different from previous
Test case 2:
1. sudo apt install efitools libguestfs-tools
2. Add CONFIG_EFI_CAPSULE_AUTHENTICATE=y to configs/sandbox_defconfig
3. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, the command needs to be run as sudo, otherwise the test_efi_capsule related test cases will be skipped, the test result can be found in comment #9
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, and mkeficapsule is a standalone tool, so the regression risk should be low
[Other Info]
* These patches are already in Lunar, so we only need to backport to Jammy |
|
2023-09-20 07:31:56 |
Heinrich Schuchardt |
description |
[Impact]
* mkeficapsule is a standalone command used to generate capsule file for updating firmware in u-boot
* mkeficapsule code exists in Jammy already, but not shipped in u-boot-tools debian package, so users are not able to generate capsule file in Jammy environment, and since the mkeficapsule command is not available in Jammy, ideally no one should be impacted.
[Test case]
Test case 1:
Users can use mkeficapsule to generate capsule file which contains firmware, or anything they want, such as dtb or fip.bin, we use mkeficapsule to create a capsule file that contains U-Boot in this test case
prerequisite:
1. Please prepare a device that is capable to use capsule file to update firmware
2. Prepare your own key by this command
$ openssl req -x509 -sha256 -newkey rsa:2048 -subj /CN=TEST_SIGNER/ -keyout SIGNER.key -out SIGNER.crt -nodes -days 365
steps:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
$ mkeficapsule --private-key SIGNER.key --certificate SIGNER.crt --monotonic-count 1 --instance 0 --index 2 --guid "12345678-abcd-1234-5678-12345678abcd" test.bin test_new.cap
2. Put the capsule file to required path(both test_new.cap and test_old.cap)
3. Reboot device and stop at u-boot prompt, then type the command. Note the actual location of test_new.cap may bedifferent in your case
=> efidebug boot add -b 0 0 mmc 0:8 test_new.cap
4. The device should reset and check if the U-Boot build stamp is different from previous
Test case 2:
1. sudo apt install efitools libguestfs-tools
2. Add CONFIG_EFI_CAPSULE_AUTHENTICATE=y to configs/sandbox_defconfig
3. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, the command needs to be run as sudo, otherwise the test_efi_capsule related test cases will be skipped, the test result can be found in comment #9
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, and mkeficapsule is a standalone tool, so the regression risk should be low
[Other Info]
* These patches are already in Lunar, so we only need to backport to Jammy |
[Impact]
* mkeficapsule is a standalone command used to generate a capsule file for updating specially configured U-Boot (not only on SD card but also on SPI flash and other media) and possibly other firmware like TF-A.
* mkeficapsule code exists in Jammy already, but is not shipped in the u-boot-tools Debian package, so users are not able to generate capsule file in Jammy environment, and since the mkeficapsule command is not available in Jammy, ideally no one should be impacted.
[Test case]
Test case 1:
Users can use mkeficapsule to generate capsule file which contains firmware, or anything they want, such as dtb or fip.bin, we use mkeficapsule to create a capsule file that contains U-Boot in this test case
prerequisite:
1. Please prepare a device that is capable to use capsule file to update firmware
2. Prepare your own key by this command
$ openssl req -x509 -sha256 -newkey rsa:2048 -subj /CN=TEST_SIGNER/ -keyout SIGNER.key -out SIGNER.crt -nodes -days 365
steps:
1. use mkeficapsule command to generate test_new.cap and test_old.cap, both contain U-Boot built at different time
$ mkeficapsule --private-key SIGNER.key --certificate SIGNER.crt --monotonic-count 1 --instance 0 --index 2 --guid "12345678-abcd-1234-5678-12345678abcd" test.bin test_new.cap
2. Put the capsule file to required path(both test_new.cap and test_old.cap)
3. Reboot device and stop at u-boot prompt, then type the command. Note the actual location of test_new.cap may bedifferent in your case
=> efidebug boot add -b 0 0 mmc 0:8 test_new.cap
4. The device should reset and check if the U-Boot build stamp is different from previous
Test case 2:
1. sudo apt install efitools libguestfs-tools
2. Add CONFIG_EFI_CAPSULE_AUTHENTICATE=y to configs/sandbox_defconfig
3. Follow the command here(https://u-boot.readthedocs.io/en/latest/develop/testing.html#pytest-suite) to test with U-Boot sandbox, the command needs to be run as sudo, otherwise the test_efi_capsule related test cases will be skipped, the test result can be found in comment #9
[Where problems could occur]
* There is no mkeficapsule command in Jammy yet, and mkeficapsule is a standalone tool, so the regression risk should be low
[Other Info]
* These patches are already in Lunar, so we only need to backport to Jammy |
|
2023-09-22 18:59:09 |
Brian Murray |
removed subscriber Ubuntu Sponsors |
|
|
|
2023-09-22 18:59:30 |
Brian Murray |
u-boot (Ubuntu): importance |
Undecided |
High |
|
2023-09-22 18:59:30 |
Brian Murray |
u-boot (Ubuntu): status |
New |
Triaged |
|
2023-09-22 21:43:29 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Brian Murray |
2023-10-14 01:17:28 |
Steve Langasek |
u-boot (Ubuntu Jammy): status |
New |
Fix Committed |
|
2023-10-14 01:17:29 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2023-10-14 01:17:34 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
2023-10-14 01:17:37 |
Steve Langasek |
tags |
oem-priority originate-from-2031356 patch |
oem-priority originate-from-2031356 patch verification-needed verification-needed-jammy |
|
2023-10-16 08:04:07 |
Aristo Chen |
attachment added |
|
mkeficapsule.log https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2036406/+attachment/5709790/+files/mkeficapsule.log |
|
2023-10-16 08:05:23 |
Aristo Chen |
tags |
oem-priority originate-from-2031356 patch verification-needed verification-needed-jammy |
oem-priority originate-from-2031356 patch verification-done-jammy verification-needed |
|
2023-11-22 06:37:39 |
Chris Halse Rogers |
u-boot (Ubuntu): status |
Triaged |
Fix Released |
|
2023-11-22 06:41:10 |
Launchpad Janitor |
u-boot (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
2023-11-22 06:41:28 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|