From: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Gidi Gal <gidi.gal.linux@gmail.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: "Invalid signature" issue on dev kernel launch
Date: Tue, 23 Mar 2021 22:25:06 -0400 [thread overview]
Message-ID: <CAFSeFg_OzVpAAH4TLXYUtrD2fgUQzj5N-ainKQuesgidkF0kwg@mail.gmail.com> (raw)
In-Reply-To: <44918.1616533727@turing-police>
[-- Attachment #1.1: Type: text/plain, Size: 1088 bytes --]
On Tue, Mar 23, 2021 at 5:09 PM Valdis Klētnieks <valdis.kletnieks@vt.edu>
wrote:
> 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:
>
I believe just after you select which kernel you wish to boot into. Check
below:
https://www.youtube.com/watch?v=bsCyZlLgrUY
>
> 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.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 1874 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-24 2:25 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
2021-03-24 2:25 ` Aruna Hewapathirane [this message]
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=CAFSeFg_OzVpAAH4TLXYUtrD2fgUQzj5N-ainKQuesgidkF0kwg@mail.gmail.com \
--to=aruna.hewapathirane@gmail.com \
--cc=gidi.gal.linux@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).