public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] welcome
Date: Sat, 4 Jun 2011 01:34:00 +0400	[thread overview]
Message-ID: <20110603213400.GA1195@openwall.com> (raw)

Hi,

This is our new mailing list for Linux kernel security hardening topics.

The intent is to use it to discuss proposed changes to the Linux kernel
before possibly bringing them to LKML, as well as to CC it on relevant
LKML threads.

We started some discussions of this nature on the owl-dev list.  We need
to bring them in here, perhaps with some over-quoting of or references
to the initial messages (archive URLs are OK).

It is also OK to discuss hardening changes that are not meant for
upstream (perhaps because we really don't expect them to be accepted).
These may find their place in distro patches, in grsecurity, etc.

Our primary focus this summer should be on getting patches submitted to
LKML, though.  This is part of Vasiliy's GSoC project.

Here's some initial info:

GSoC: overview of grsecurity and -ow patches:
http://www.openwall.com/lists/owl-dev/2011/04/23/1

https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening

Vasiliy's report #1:
http://www.openwall.com/lists/owl-dev/2011/05/18/1
(and lots of further messages in that thread - click "thread-next")

Vasiliy's report #2:
http://www.openwall.com/lists/owl-dev/2011/05/25/1

Vasiliy's report #3:
http://www.openwall.com/lists/owl-dev/2011/05/31/3

procfs mount options:
http://www.openwall.com/lists/owl-dev/2011/06/03/3

Let's start.

Alexander

                 reply	other threads:[~2011-06-03 21:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110603213400.GA1195@openwall.com \
    --to=solar@openwall.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox