From: Kees Cook <keescook@chromium.org>
To: Solar Designer <solar@openwall.com>
Cc: Jann Horn <jannh@google.com>, "Theodore Y. Ts'o" <tytso@mit.edu>,
Kernel Hardening <kernel-hardening@lists.openwall.com>,
linux-hardening@vger.kernel.org
Subject: Re: Linux-specific kernel hardening
Date: Wed, 7 Oct 2020 00:05:40 -0700 [thread overview]
Message-ID: <202010070003.466BA35@keescook> (raw)
In-Reply-To: <20201006142127.GA10613@openwall.com>
On Tue, Oct 06, 2020 at 04:21:27PM +0200, Solar Designer wrote:
> On Mon, Oct 05, 2020 at 03:39:26PM -0700, Kees Cook wrote:
> > On Tue, Oct 06, 2020 at 12:26:50AM +0200, Jann Horn wrote:
> > > On Mon, Oct 5, 2020 at 6:48 PM Solar Designer <solar@openwall.com> wrote:
> > > > If 100% of the topics on linux-hardening are supposed to be a subset of
> > > > what was on kernel-hardening, I think it'd be OK for me to provide the
> > > > subscriber list to a vger admin, who would subscribe those people to
> > > > linux-hardening.
> > >
> > > (if folks want to go that route, probably easier to subscribe the list
> > > linux-hardening@ itself to kernel-hardening@ instead of syncing
> > > subscriber lists?)
> >
> > Yeah, that would make things a bit simpler. Solar, would you be willing
> > to do that? (Then I can tweak the wiki instructions a bit more.)
>
> Sure, I can do that. Should I?
>
> Per http://vger.kernel.org/vger-lists.html#linux-hardening there are
> currently 39 subscribers on the new list. I guess most of those are
> also on kernel-hardening, and would start receiving two copies of
> messages that are posted to kernel-hardening. I guess they would then
> need to unsubscribe from kernel-hardening if they want to see the
> content of both lists, or to unsubscribe from linux-hardening if they
> changed their mind and only want the content of kernel-hardening. I
> think this is still not too many people, so this is reasonable; if we
> were to do it later, we'd inconvenience more people.
Hm, I guess I was thinking about this only from the perspective of
Message-Id handling: the duplicates wouldn't be noticed -- but of course
I've been struggling with IMAP vs Gmail for so long I've almost
forgotten how actual email works. ;)
Yeah, the duplicate emails would be pretty bad. Let's not do this for
now, and if it becomes an actual issue we can change it then.
--
Kees Cook
next prev parent reply other threads:[~2020-10-07 7:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 17:14 Linux-specific kernel hardening Kees Cook
2020-09-29 19:25 ` Solar Designer
2020-09-29 23:41 ` Kees Cook
2020-09-30 9:02 ` Solar Designer
2020-10-05 14:14 ` Solar Designer
2020-10-05 16:02 ` Theodore Y. Ts'o
2020-10-05 16:48 ` Solar Designer
2020-10-05 22:26 ` Jann Horn
2020-10-05 22:39 ` Kees Cook
2020-10-06 14:21 ` Solar Designer
2020-10-07 7:05 ` Kees Cook [this message]
2020-10-05 22:23 ` Kees Cook
2020-10-07 15:16 ` Romain Perier
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=202010070003.466BA35@keescook \
--to=keescook@chromium.org \
--cc=jannh@google.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-hardening@vger.kernel.org \
--cc=solar@openwall.com \
--cc=tytso@mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).