linux-kernel - Re: [PATCH] kbuild: Use objtree for module signing key path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176116758389.2674526.2727622391816025420.b4-ty@kernel.org>
Date: Wed, 22 Oct 2025 23:20:40 +0200
From: Nicolas Schier <nsc@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>,
	Nicolas Schier <nicolas.schier@...ux.dev>,
	Masahiro Yamada <masahiroy@...nel.org>,
	mike.malyshev@...il.com
Cc: Nicolas Schier <nsc@...nel.org>,
	linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kbuild: Use objtree for module signing key path


On Wed, 15 Oct 2025 16:34:52 +0000, mike.malyshev@...il.com wrote:
> When building out-of-tree modules with CONFIG_MODULE_SIG_FORCE=y,
> module signing fails because the private key path uses $(srctree)
> while the public key path uses $(objtree). Since signing keys are
> generated in the build directory during kernel compilation, both
> paths should use $(objtree) for consistency.
> 
> This causes SSL errors like:
>   SSL error:02001002:system library:fopen:No such file or directory
>   sign-file: /kernel-src/certs/signing_key.pem
> 
> [...]

Applied to kbuild-next, thanks!

[1/1] kbuild: Use objtree for module signing key path
      commit: d30ea149386168d3b1a3fb213523ca6512c07e9f

Please note that commit hashes might change in case of issues with
kbuild-next branch.

Best regards,
-- 
Nicolas