| 2022-10-20 11:14:14 |
Aaron Rainbolt |
bug |
|
|
added bug |
| 2022-10-20 11:19:58 |
Aaron Rainbolt |
description |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option.
3: Reboot, prepare the system for use by the end user (just double-click the shortcut), then reboot again.
4: Finish setup.
5: Run "ls /var/lib/shim-signed/mok".'
Expected result: The files "MOK.priv" and "MOK.der" should be shown.
Actual result: The listed directory is empty.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option. Make sure to allow the installation of proprietary drivers and choose to configure Secure Boot.
3: Reboot and do the key enrollment with mokutil.
4: Reboot again, then prepare the system for use by the end user (just double-click the shortcut), then reboot again.
5: Finish setup.
6: Run "ls /var/lib/shim-signed/mok".'
Expected result: The files "MOK.priv" and "MOK.der" should be shown.
Actual result: The listed directory is empty.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
|
| 2022-10-20 12:05:54 |
Aaron Rainbolt |
description |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option. Make sure to allow the installation of proprietary drivers and choose to configure Secure Boot.
3: Reboot and do the key enrollment with mokutil.
4: Reboot again, then prepare the system for use by the end user (just double-click the shortcut), then reboot again.
5: Finish setup.
6: Run "ls /var/lib/shim-signed/mok".'
Expected result: The files "MOK.priv" and "MOK.der" should be shown.
Actual result: The listed directory is empty.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option. Make sure to allow the installation of proprietary drivers and choose to configure Secure Boot.
3: Reboot and do the key enrollment with mokutil.
4: Reboot again, open a terminal, and run "ls /var/lib/shim-signed/mok".
Expected result: The files "MOK.priv" and "MOK.der" should be shown.
Actual result: The listed directory is empty.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
|
| 2022-10-20 12:09:34 |
Aaron Rainbolt |
description |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option. Make sure to allow the installation of proprietary drivers and choose to configure Secure Boot.
3: Reboot and do the key enrollment with mokutil.
4: Reboot again, open a terminal, and run "ls /var/lib/shim-signed/mok".
Expected result: The files "MOK.priv" and "MOK.der" should be shown.
Actual result: The listed directory is empty.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
Steps to reproduce:
1: Enable Secure Boot.
2: Install the latest Ubuntu Kinetic ISO using the OEM installation option. Make sure to allow the installation of proprietary drivers and choose to configure Secure Boot.
3: Reboot and do the key enrollment with mokutil.
4: Reboot again, open a terminal, and run "ls /var/lib/shim-signed/mok". Then prepare the system for the end user (double-clicking the shortcut on the desktop).
5: Reboot again, then finish setup.
6: Run "ls /var/lib/shim-signed/moK" again.
Expected result: The files "MOK.priv" and "MOK.der" should be shown with each "ls" command.
Actual result: The listed directory is empty both times.
Notes:
This did NOT happen to me on a non-OEM installation. I noticed it attempting to manually sign a driver while grappling with bug 1991725. It probably will interfere with the use of DKMS modules even if they get installed and signed properly the first time.
For some reason "ubuntu-bug shim-signed" thought that shim-signed wasn't an official Ubuntu package, so I'm reporting this without using ubuntu-bug. I can provide any desired log files from the test system upon request. |
|
| 2022-10-21 01:57:53 |
Steve Langasek |
affects |
shim-signed (Ubuntu) |
ubiquity (Ubuntu) |
|
| 2022-10-24 19:18:15 |
Dan Bungert |
ubiquity (Ubuntu): importance |
Undecided |
Low |
|
| 2022-10-24 19:18:41 |
Dan Bungert |
ubiquity (Ubuntu): status |
New |
Triaged |
|
