From: "Peter Böhm" <peter.bo@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to disable the modules service?
Date: Sun, 23 Oct 2022 17:04:58 +0200 [thread overview]
Message-ID: <12080132.O9o76ZdvQC@big> (raw)
In-Reply-To: <25429.19845.935650.644014@tux.local>
Rainer,
the handbook still recommends to build sound modules (and many many others) as
module, because it is easier than doing a static configuration. Now, you can
ask, why someone wants to build it static into the kernel. The answer is:
Security !
Maybe you know this wiki article:
https://wiki.gentoo.org/wiki/Signed_kernel_module_support
This is a pre-condition for enabling LOCKDOWN in the kernel ... OR ... you
have NO modules support (=monolithic kernel) ! So, you have the choice which
way you want to go.
I am using a monolithic kernel also. Dont try to enable lockdown in your
kernel if you use unsigned modules. ;-) I wrote a big warning in my wiki
article:
https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/
Kernel_Hardening_with_KSPP
Regards,
Peter
Am Sonntag, 23. Oktober 2022, 16:19:49 CEST schrieb Dr Rainer Woitok:
> Peter,
>
> On Sunday, 2022-10-23 12:45:42 +0200, you wrote:
> > ...
> > we have a wiki article for this:
> > https://wiki.gentoo.org/wiki/Kernel_Modules#Going_completely_.22module-les
> > s.22
> When I built my first Gentoo system in 2019, the Handbook instructed to
> build anything sound related as modules, if I remember correctly. Is
> this no longer true?
>
> Sincerely,
> Rainer
prev parent reply other threads:[~2022-10-23 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 9:56 [gentoo-user] How to disable the modules service? Dex Conner
2022-10-23 10:45 ` Peter Böhm
2022-10-23 11:29 ` Dex Conner
2022-10-23 11:42 ` Dale
2022-10-23 15:35 ` Neil Bothwick
2022-10-24 5:58 ` Dex Conner
2022-10-23 14:19 ` Dr Rainer Woitok
2022-10-23 15:04 ` Peter Böhm [this message]
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=12080132.O9o76ZdvQC@big \
--to=peter.bo@web.de \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox