Linux kernel signing process

Pages (3): Previous 1 2 3 Next

puglife4me
Junior Member

03-21-2016, 08:37 PM

#11

You didn't realize you set up Ubuntu on a different machine and transferred it, which could explain the booting issue.

puglife4me

03-21-2016, 08:37 PM #11

You didn't realize you set up Ubuntu on a different machine and transferred it, which could explain the booting issue.

MWRH2002
Junior Member

03-22-2016, 09:17 AM

#12

No, this shouldn't relate to anything... A query about how the new kernel was installed. Was it an official update? If not, it isn't clearly marked as a signed Linux kernel EFI image from Microsoft. Edited February 13, 2019 by Guest

MWRH2002

03-22-2016, 09:17 AM #12

mic_max
Member

03-26-2016, 05:36 PM

#13

I completed those actions but encountered an issue at the fifth stage due to a signature problem.

mic_max

03-26-2016, 05:36 PM #13

I completed those actions but encountered an issue at the fifth stage due to a signature problem.

TazBazuk
Member

04-15-2016, 07:38 AM

#14

Is not signed... There is nothing you can do about that afaik... Isn't that issued fixed on newer versions of Ubuntu? you could run a chroot environment from a live USB and update from there

TazBazuk

04-15-2016, 07:38 AM #14

Is not signed... There is nothing you can do about that afaik... Isn't that issued fixed on newer versions of Ubuntu? you could run a chroot environment from a live USB and update from there

Nevla
Member

207

04-16-2016, 07:23 PM

#15

The problem is resolved in the latest release, but my BIOS is already damaged and newer updates won’t help. The kernel I’m attempting to start was designed to fix this exact issue. Can you sign the kernel yourself so you can boot from it? I’m not comfortable with chroot, so I’m unsure if that would be useful.

Nevla

04-16-2016, 07:23 PM #15

ALECdaMAN123
Member

04-17-2016, 09:48 PM

#16

Yes, resetting CMOS removes secure boot settings. Ensure you can still boot after the reset.

ALECdaMAN123

04-17-2016, 09:48 PM #16

Yes, resetting CMOS removes secure boot settings. Ensure you can still boot after the reset.

ThatTunerGuy
Junior Member

05-02-2016, 08:19 AM

#17

I have reinitialized the CMOS, but it appears the issue remains or secure boot is still active by default.

ThatTunerGuy

05-02-2016, 08:19 AM #17

I have reinitialized the CMOS, but it appears the issue remains or secure boot is still active by default.

Amtrak10
Senior Member

639

05-02-2016, 09:36 AM

#18

I've examined the problem thoroughly; it doesn't appear to have a straightforward fix. The signing process should involve retrieving the keys from your device, but if you can't access the BIOS, I'm uncertain about the steps. You might consider removing the BIOS chip and reprogramming it using a programmer. Alternatively, you could set up a launchpad account and reach out to the Ubuntu developers via the bug report—several people are discussing this secure boot issue. If you're willing to wait, I could attempt signing the kernel image, though I have no guarantee it will work on your system. Edited February 14, 2019 by Guest

Amtrak10

05-02-2016, 09:36 AM #18

bear7001
Senior Member

448

05-07-2016, 06:20 AM

#19

There might be an older GRUB2 release that supports unsigned kernels, but I haven't confirmed it. You can check the linked bug report for details.

bear7001

05-07-2016, 06:20 AM #19

There might be an older GRUB2 release that supports unsigned kernels, but I haven't confirmed it. You can check the linked bug report for details.

ilija
Member

206

05-07-2016, 06:48 AM

#20

No one shared the exact issue, making it hard to confirm its validity. You might also pick that particular version of the malware. Probably, auto signing isn't feasible without you adding your custom keys to the BIOS.

ilija

05-07-2016, 06:48 AM #20

Pages (3): Previous 1 2 3 Next