From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Gidi Gal <gidi.gal.linux@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: "Invalid signature" issue on dev kernel launch
Date: Tue, 23 Mar 2021 17:08:47 -0400 [thread overview]
Message-ID: <44918.1616533727@turing-police> (raw)
In-Reply-To: <CAB+0Vo=sf=fxHyqvC=d5Yka00EnRbwuCpJFJvSbg09e7cK9VMg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 633 bytes --]
On Tue, 23 Mar 2021 18:36:58 +0200, Gidi Gal said:
> knowledge on this subject), I am now facing "invalid signature" error when
> I reboot with my installed dev kernel.
When/where exactly are you getting that error? There's three major
places where things can go wrong:
1) If you're using secure boot, and the grub2 stuff isn't signed by
a certificate your BIOS/EFI knows about.
2) If you're using secure boot, and the kernel itself isn't signed by
a certificate that grub2 knows about.
3) If your kernel config says modules have to be signed, and a module
isn't properly signed with a certificate that your kernel knows about.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-03-23 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:36 "Invalid signature" issue on dev kernel launch Gidi Gal
2021-03-23 21:08 ` Valdis Klētnieks [this message]
2021-03-24 2:25 ` Aruna Hewapathirane
2021-03-24 2:20 ` Aruna Hewapathirane
2021-03-24 2:36 ` Aruna Hewapathirane
2021-03-24 5:26 ` Valdis Klētnieks
2021-03-24 13:21 ` Aruna Hewapathirane
2021-03-24 14:59 ` Valdis Klētnieks
2021-03-24 12:58 ` Gidi Gal
2021-03-24 13:26 ` Aruna Hewapathirane
2021-03-24 15:17 ` Valdis Klētnieks
2021-03-24 13:12 ` Gidi Gal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44918.1616533727@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=gidi.gal.linux@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.