From: Kees Cook <keescook@chromium.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Salvatore Mesoraca <s.mesoraca16@gmail.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Laura Abbott <labbott@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [RFC] kconfig: add hardened defconfig helpers
Date: Sat, 28 Jul 2018 13:11:05 -0700 [thread overview]
Message-ID: <CAGXu5jL2s-Dv+4mFV3Wwev51kcQ3h5M02UoH6K71s_NqeXw1yw@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNASyzWvJ6Bf1Zp4k=B-QFOHEg7YqeFErA2Gg9PNZadvuew@mail.gmail.com>
On Sun, Jul 22, 2018 at 6:55 PM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> 2018-07-20 14:15 GMT+09:00 Kees Cook <keescook@chromium.org>:
>> +lkml, Masahiro, and linux-doc, just for wider review/thoughts.
>
>
> I do not subscribe to kernel-hardening ML.
>
> I do not see the original patch in lkml or kbuild/kconfig ML.
Here's the start of the thread:
http://www.openwall.com/lists/kernel-hardening/2018/07/18/1
-Kees
--
Kees Cook
Pixel Security
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Salvatore Mesoraca <s.mesoraca16@gmail.com>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
Laura Abbott <labbott@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [RFC] kconfig: add hardened defconfig helpers
Date: Sat, 28 Jul 2018 13:11:05 -0700 [thread overview]
Message-ID: <CAGXu5jL2s-Dv+4mFV3Wwev51kcQ3h5M02UoH6K71s_NqeXw1yw@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNASyzWvJ6Bf1Zp4k=B-QFOHEg7YqeFErA2Gg9PNZadvuew@mail.gmail.com>
On Sun, Jul 22, 2018 at 6:55 PM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
> 2018-07-20 14:15 GMT+09:00 Kees Cook <keescook@chromium.org>:
>> +lkml, Masahiro, and linux-doc, just for wider review/thoughts.
>
>
> I do not subscribe to kernel-hardening ML.
>
> I do not see the original patch in lkml or kbuild/kconfig ML.
Here's the start of the thread:
http://www.openwall.com/lists/kernel-hardening/2018/07/18/1
-Kees
--
Kees Cook
Pixel Security
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-28 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 17:38 [RFC] kconfig: add hardened defconfig helpers Salvatore Mesoraca
2018-07-18 20:09 ` Jann Horn
2018-07-19 10:35 ` Salvatore Mesoraca
2018-07-20 5:15 ` Kees Cook
2018-07-20 5:15 ` Kees Cook
2018-07-20 13:37 ` Eric W. Biederman
2018-07-20 13:37 ` Eric W. Biederman
2018-07-30 16:19 ` Salvatore Mesoraca
2018-07-30 16:19 ` Salvatore Mesoraca
2018-07-23 1:55 ` Masahiro Yamada
2018-07-23 1:55 ` Masahiro Yamada
2018-07-28 20:11 ` Kees Cook [this message]
2018-07-28 20:11 ` Kees Cook
2018-07-30 16:11 ` Salvatore Mesoraca
2018-07-30 16:11 ` Salvatore Mesoraca
2018-07-30 16:54 ` Kees Cook
2018-07-30 16:54 ` Kees Cook
2018-07-31 7:43 ` Salvatore Mesoraca
2018-07-31 7:43 ` Salvatore Mesoraca
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=CAGXu5jL2s-Dv+4mFV3Wwev51kcQ3h5M02UoH6K71s_NqeXw1yw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.mesoraca16@gmail.com \
--cc=yamada.masahiro@socionext.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.