We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems there is a problem with the current stable kernel (5.15.14 at the date of this issue).
The kernel option TRIM_UNUSED_KSYMS is defined in my config as:
Symbol: TRIM_UNUSED_KSYMS [=n] Type : bool Defined at init/Kconfig:2301 Prompt: Trim unused exported kernel symbols Depends on: MODULES [=n] && !COMPILE_TEST [=n] Visible if: MODULES [=n] && !COMPILE_TEST [=n] && EXPERT [=y] Location: (1) -> Enable loadable module support (MODULES [=n])
Or the script (with the setup above) outputs me: CONFIG_TRIM_UNUSED_KSYMS | y | my | cut_attack_surface | FAIL: not found
But as the hardening requires to have MODULES = n (is not set) it is impossible to set TRIM_UNUSED_KSYMS through menuconfig.
The text was updated successfully, but these errors were encountered:
Fix TRIM_UNUSED_KSYMS check
7ed482b
TRIM_UNUSED_KSYMS can't be enabled if MODULES are disabled. Thanks to @Churam for reporting. Refers to #58.
@Churam thanks for your report!
Fixed.
The output for your case now:
CONFIG_TRIM_UNUSED_KSYMS | y | my | cut_attack_surface | OK: CONFIG_MODULES "is not set"
Sorry, something went wrong.
Fix OK Output is now as expected, closing issue
No branches or pull requests
It seems there is a problem with the current stable kernel (5.15.14 at the date of this issue).
The kernel option TRIM_UNUSED_KSYMS is defined in my config as:
Or the script (with the setup above) outputs me:
CONFIG_TRIM_UNUSED_KSYMS | y | my | cut_attack_surface | FAIL: not found
But as the hardening requires to have MODULES = n (is not set) it is impossible to set TRIM_UNUSED_KSYMS through menuconfig.
The text was updated successfully, but these errors were encountered: