Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Arnout Engelen <arnout@bzzt.net>
Cc: linux@weissschuh.net, arnd@arndb.de, da.gomez@samsung.com,
	linux-arch@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	masahiroy@kernel.org, nathan@kernel.org, nicolas@fjasle.eu,
	petr.pavlu@suse.com, samitolvanen@google.com
Subject: Re: [PATCH RFC 2/2] module: Introduce hash-based integrity checking
Date: Fri, 10 Jan 2025 11:16:40 -0800	[thread overview]
Message-ID: <Z4FyGEXBK4EUi_Oq@bombadil.infradead.org> (raw)
In-Reply-To: <20250109105227.1012778-1-arnout@bzzt.net>

On Thu, Jan 09, 2025 at 11:52:27AM +0100, Arnout Engelen wrote:
> On Fri, 3 Jan 2025 17:37:52 -0800, Luis Chamberlain wrote:
> > What distro which is using module signatures would switch
> > to this as an alternative instead?
> 
> In NixOS, we disable MODULE_SIG by default (because we value
> reproducibility over having module signatures). Enabling
> MODULE_HASHES on systems that do not need to load out-of-tree
> modules would be a good step forward.
> 

Mentioning this in the cover letter will also be good. So two
distros seemt to want this.

  Luis

  reply	other threads:[~2025-01-10 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 22:51 [PATCH RFC 0/2] module: Introduce hash-based integrity checking Thomas Weißschuh
2024-12-25 22:51 ` [PATCH RFC 1/2] kbuild: add stamp file for vmlinux BTF data Thomas Weißschuh
2024-12-25 22:52 ` [PATCH RFC 2/2] module: Introduce hash-based integrity checking Thomas Weißschuh
2025-01-04  1:37   ` Luis Chamberlain
2025-01-04  6:30     ` Thomas Weißschuh
2025-01-08 19:08       ` Luis Chamberlain
2025-01-13  9:15     ` Fabian Grünbichler
2025-01-09 10:52   ` Arnout Engelen
2025-01-10 19:16     ` Luis Chamberlain [this message]
2025-01-13 15:09       ` Petr Pavlu

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=Z4FyGEXBK4EUi_Oq@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnout@bzzt.net \
    --cc=da.gomez@samsung.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.com \
    /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