From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
Mirsad Goran Todorovac <mirsad.goran.todorovac@alu.hr>
Cc: linux-kernel@vger.kernel.org,
Linux Kernel Build System <linux-kbuild@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [BUILD] [FOUND WORKAROUND] Unable to sign drivers on Ubuntu 22.04 LTS desktop
Date: Fri, 5 May 2023 19:45:32 +0700 [thread overview]
Message-ID: <ba8a28bc-d390-0ece-a4b0-e20ff0e95504@gmail.com> (raw)
In-Reply-To: <59599649-6481-eb3a-8584-6653f2c511cd@alu.unizg.hr>
On 5/5/23 16:00, Mirsad Goran Todorovac wrote:
> Hi all,
>
> There was no success in building 6.3+ with the Ubuntu generic config, but it has succeeded
> with the config derived from Debian one.
>
> Still, it would be interesting to find what is preventing the Ubuntu config from signing the
> kernel modules. Up to that point the build process is fine.
>
You will need to see Documentation/admin-guide/module-signing.rst.
Especially on "Generating signing keys", there are instructions on
generating your own signing key, because in most cases you don't
have access to signing keys from your distribution.
Anyway, when you have problems related to building kernel, always
Cc: linux-kbuild list.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-05-05 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 17:02 [BUILD] Unable to sign drivers on Ubuntu 22.04 LTS desktop Mirsad Goran Todorovac
2023-05-05 9:00 ` [BUILD] [FOUND WORKAROUND] " Mirsad Goran Todorovac
2023-05-05 12:45 ` Bagas Sanjaya [this message]
2023-05-05 13:46 ` [BUILD] " Bagas Sanjaya
2023-05-05 20:07 ` Mirsad Goran Todorovac
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=ba8a28bc-d390-0ece-a4b0-e20ff0e95504@gmail.com \
--to=bagasdotme@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mirsad.goran.todorovac@alu.hr \
--cc=mirsad.todorovac@alu.unizg.hr \
/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