From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: kernel-hardening@lists.openwall.com
Subject: "Hardened" tree on kernel.org?
Date: Fri, 31 Aug 2018 13:44:06 -0400 [thread overview]
Message-ID: <20180831174406.GA1702@chatter> (raw)
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Hi, all:
There's a lot of excellent work being done on this list and as part of
KSPP that enjoys limited exposure due to long and arduous upstreaming
process. I am wondering if some of the proposed changes would see wider
testing if there was a curated semi-official "hardened" tree hosted on
kernel.org that would carry kernel hardening patches proposed for
inclusion into mainline. There is at least one project that does
something like this:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
though there's the distinction that, to my knowledge, RT is not intended
to be upstreamed.
I think wider testing and adoption would be easier if there was a place
for folks to download a "hardened Linux tarball" -- with the
understanding that it would include features that may or may not
eventually make it into mainline. I know it's a lot of work, and I'm
certainly not volunteering for it (I don't have the right set of skills
for this), but I believe there is a demand for such resource among
security enthusiasts and security-minded distros.
In a sense, this would shadow Greg's work -- taking the latest stable
tree and porting a hardening patchset on top of it. Maybe one of the LTS
trees, too?
Do you think this would be a worthwhile thing, or would that distract
from overall mainlining goals?
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2018-08-31 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 17:44 Konstantin Ryabitsev [this message]
2018-09-10 12:24 ` "Hardened" tree on kernel.org? Yves-Alexis Perez
2018-09-10 16:03 ` Kees Cook
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=20180831174406.GA1702@chatter \
--to=konstantin@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.