From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>, Christoph Hellwig <hch@infradead.org>
Cc: "Roberts, William C" <william.c.roberts@intel.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] printk: introduce kptr_restrict level 3
Date: Thu, 06 Oct 2016 14:19:48 -0700 [thread overview]
Message-ID: <1475788788.1820.4.camel@perches.com> (raw)
In-Reply-To: <CAGXu5jJsj=4=j1R6aUYiDvdWqY916pJbBdXCEbQFFoyQ0QP4Yw@mail.gmail.com>
On Thu, 2016-10-06 at 14:00 -0700, Kees Cook wrote:
> And based on my read of this thread, we all appear to be in violent
> agreement. :) "always protect %p" is absolutely the goal, and we can
> figure out the best way to get there.
I proposed emitting pointers from the const and text sections by default
and using NULL for data pointers.
https://lkml.org/lkml/2016/8/5/380
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>, Christoph Hellwig <hch@infradead.org>
Cc: "Roberts, William C" <william.c.roberts@intel.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [kernel-hardening] Re: [PATCH] printk: introduce kptr_restrict level 3
Date: Thu, 06 Oct 2016 14:19:48 -0700 [thread overview]
Message-ID: <1475788788.1820.4.camel@perches.com> (raw)
In-Reply-To: <CAGXu5jJsj=4=j1R6aUYiDvdWqY916pJbBdXCEbQFFoyQ0QP4Yw@mail.gmail.com>
On Thu, 2016-10-06 at 14:00 -0700, Kees Cook wrote:
> And based on my read of this thread, we all appear to be in violent
> agreement. :) "always protect %p" is absolutely the goal, and we can
> figure out the best way to get there.
I proposed emitting pointers from the const and text sections by default
and using NULL for data pointers.
https://lkml.org/lkml/2016/8/5/380
next prev parent reply other threads:[~2016-10-06 21:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 18:04 [PATCH] printk: introduce kptr_restrict level 3 william.c.roberts
2016-10-05 18:04 ` [kernel-hardening] " william.c.roberts
2016-10-05 19:34 ` Kees Cook
2016-10-05 19:34 ` [kernel-hardening] " Kees Cook
2016-10-06 13:17 ` Roberts, William C
2016-10-06 13:17 ` [kernel-hardening] " Roberts, William C
2016-10-06 15:18 ` Roberts, William C
2016-10-06 21:04 ` [kernel-hardening] " Kees Cook
2016-10-07 14:19 ` [kernel-hardening] " Roberts, William C
2016-10-07 14:29 ` Jann Horn
2016-10-07 15:05 ` Roberts, William C
2016-10-07 15:15 ` Jann Horn
2016-10-07 19:12 ` Kees Cook
2016-10-11 18:11 ` Roberts, William C
2016-10-05 20:52 ` Rasmus Villemoes
2016-10-05 20:52 ` [kernel-hardening] " Rasmus Villemoes
2016-10-06 13:23 ` Roberts, William C
2016-10-06 13:23 ` [kernel-hardening] " Roberts, William C
2016-10-06 13:31 ` Christoph Hellwig
2016-10-06 13:31 ` [kernel-hardening] " Christoph Hellwig
2016-10-06 13:47 ` Roberts, William C
2016-10-06 13:47 ` [kernel-hardening] " Roberts, William C
2016-10-06 13:56 ` Christoph Hellwig
2016-10-06 13:56 ` [kernel-hardening] " Christoph Hellwig
2016-10-06 14:59 ` Roberts, William C
2016-10-06 14:59 ` [kernel-hardening] " Roberts, William C
2016-10-06 21:00 ` Kees Cook
2016-10-06 21:00 ` [kernel-hardening] " Kees Cook
2016-10-06 21:19 ` Joe Perches [this message]
2016-10-06 21:19 ` Joe Perches
2016-10-06 21:25 ` Kees Cook
2016-10-06 21:25 ` [kernel-hardening] " Kees Cook
2016-10-07 14:21 ` Roberts, William C
2016-10-07 14:21 ` [kernel-hardening] " Roberts, William C
2016-10-06 14:05 ` Jann Horn
2016-10-06 14:05 ` Jann Horn
2016-10-06 14:46 ` Jann Horn
2016-10-06 14:46 ` Jann Horn
2016-10-07 11:52 ` Jann Horn
2016-10-07 11:52 ` Jann Horn
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=1475788788.1820.4.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=william.c.roberts@intel.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.