From: Sam James <sam@gentoo.org>
To: Kees Cook <keescook@chromium.org>
Cc: Salvatore Mesoraca <s.mesoraca16@gmail.com>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
kernel@gentoo.org
Subject: Re: [PATCH] hardening: Provide Kconfig fragments for basic options
Date: Sat, 02 Sep 2023 07:35:07 +0100 [thread overview]
Message-ID: <87ledpcc92.fsf@gentoo.org> (raw)
In-Reply-To: <20230825050618.never.197-kees@kernel.org>
Kees Cook <keescook@chromium.org> writes:
> Inspired by Salvatore Mesoraca's earlier[1] efforts to provide some
> in-tree guidance for kernel hardening Kconfig options, add a new fragment
> named "hardening-basic.config" (along with some arch-specific fragments)
> that enable a basic set of kernel hardening options that have the least
> (or no) performance impact and remove a reasonable set of legacy APIs.
>
> Using this fragment is as simple as running "make hardening.config".
>
> More extreme fragments can be added[2] in the future to cover all the
> recognized hardening options, and more per-architecture files can be
> added too.
>
> For now, document the fragments directly via comments. Perhaps .rst
> documentation can be generated from them in the future (rather than the
> other way around).
>
This is likely to make life a bit easier for us downstream in Gentoo,
where we currently supply a patch for KSPP:
https://gitweb.gentoo.org/proj/linux-patches.git/tree/4567_distro-Gentoo-Kconfig.patch?h=6.4#n237.
> [1] https://lore.kernel.org/kernel-hardening/1536516257-30871-1-git-send-email-s.mesoraca16@gmail.com/
> [2] https://github.com/KSPP/linux/issues/14
best,
sam
prev parent reply other threads:[~2023-09-02 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 5:06 [PATCH] hardening: Provide Kconfig fragments for basic options Kees Cook
2023-09-02 6:35 ` Sam James [this message]
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=87ledpcc92.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=keescook@chromium.org \
--cc=kernel@gentoo.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.mesoraca16@gmail.com \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).