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: <176959965189.1301244.15814296328206965994.b4-ty@kernel.org>
Date: Wed, 28 Jan 2026 12:27:31 +0100
From: Nicolas Schier <nsc@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Uday Shankar <ushankar@...estorage.com>, 
 Masahiro Yamada <masahiroy@...nel.org>, linux-kbuild@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Holger Kiehl <Holger.Kiehl@....de>
Subject: Re: [PATCH] kbuild: rpm-pkg: Generate debuginfo package manually

On Wed, 21 Jan 2026 15:29:15 -0700, Nathan Chancellor wrote:
> Commit a7c699d090a1 ("kbuild: rpm-pkg: build a debuginfo RPM") adjusted
> the __spec_install_post macro to include __os_install_post, which runs
> brp-strip. This ends up stripping module signatures, breaking loading
> modules with lockdown enabled.
> 
> Undo most of the changes of the aforementioned debuginfo patch and
> mirror commit 16c36f8864e3 ("kbuild: deb-pkg: use build ID instead of
> debug link for dbg package") in kernel.spec to generate a functionally
> equivalent debuginfo package while avoiding touching the modules after
> they have already been signed during modules_install.
> 
> [...]

Applied to kbuild/linux.git (kbuild-fixes-unstable), thanks!

[1/1] kbuild: rpm-pkg: Generate debuginfo package manually
      https://git.kernel.org/kbuild/c/62089b80

Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped,
reverted or modified (e.g. trailers). Patches applied to the
kbuild-fixes-unstable branch are accepted pending wider testing in
linux-next and any post-commit review; they will generally be moved
to the kbuild-fixes branch in a week if no issues are found.

Best regards,
-- 
Nicolas



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ