DRAFT : Proposed kernel configuration improvements to enhance security#1816
Draft
aluciani wants to merge 1 commit intolinuxboot:masterfrom
Draft
DRAFT : Proposed kernel configuration improvements to enhance security#1816aluciani wants to merge 1 commit intolinuxboot:masterfrom
aluciani wants to merge 1 commit intolinuxboot:masterfrom
Conversation
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
Oct 20, 2024
…atch for qemu board Before commiting changes here, take nv41 linux config changes and save into patch file: git diff > patch Signed-off-by: Thierry Laurion <insurgo@riseup.net>
tlaurion
added a commit
to tlaurion/heads
that referenced
this pull request
Oct 20, 2024
…g but flashrom Apply previous patch: patch config/linux-qemu.config patch Apply changes: docker run -e DISPLAY=$DISPLAY --network host --rm -ti -v $(pwd):$(pwd) -w $(pwd) tlaurion/heads-dev-env:latest -- make BOARD=qemu-coreboot-whiptail-tpm1 linux.modify_and_save_oldconfig_in_place Review changes, build: docker run -e DISPLAY=$DISPLAY --network host --rm -ti -v $(pwd):$(pwd) -w $(pwd) tlaurion/heads-dev-env:latest -- make BOARD=qemu-coreboot-whiptail-tpm1 Run: docker run -e DISPLAY=$DISPLAY --network host --rm -ti -v $(pwd):$(pwd) -w $(pwd) tlaurion/heads-dev-env:latest -- make BOARD=qemu-coreboot-whiptail-tpm1 run Signed-off-by: Thierry Laurion <insurgo@riseup.net>
Collaborator
Collaborator
|
@aluciani as noted under CI, commits unsigned fail CI at https://github.com/linuxboot/heads/pull/1816/checks?check_run_id=31787361888 |
Collaborator
|
@aluciani this is nice exercise. Wondering if https://github.com/a13xp0p0v/kernel-hardening-checker should be added under nix docker image and some self-test should be added in CI in long term to make those checks automatic and warn of security regressions, somehow. Note that final change on nv41 linux config file can be observed directly under https://github.com/linuxboot/heads/pull/1817/files#diff-782b88c1e0e03988fb8336bd99c65310869be9f3c1e3a88a1be57bcd5ab7c4e8 |
Signed-off-by: Antoine Luciani <97607910+aluciani@users.noreply.github.com>
3131a61 to
a9a1b20
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was looking at heads' kernel config (for nitropad-nv41 in my case), and I thought there might be some options that would be worth changing (“y”->“is not set”, “is not set”->“y” and some literal values).
This idea comes to me from a13xp0p0v's project kernel-hardening-checker, which aims to verify the security of a linux kernel. It's true that this project is more for server or desktop linux, but I think some options could be useful in the case of head.
I'm talking about the following options:
From "y" to "is not set" :
From to "is not set" to "y" :
Literal values :
Please note that some options are changed automatically, but only after running the command “make BOARD=nitropad-nv41 linux.prompt_for_new_config_options_for_kernel_version_bump”.
This is a draft, so I haven't checked whether it's really a problem to change the GCC version, etc, at the moment.
I'm adding a mod.md file here, which lists all the modules and linux CONFIGs required for traceability.
obviously DO NOT merge