From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jiri Kosina <jikos@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Security
Date: Sun, 23 Sep 2018 14:34:07 -0400 [thread overview]
Message-ID: <20180923183407.GA2774@thunk.org> (raw)
In-Reply-To: <nycvar.YFH.7.76.1809231518440.15880@cbobk.fhfr.pm>
On Sun, Sep 23, 2018 at 03:20:22PM +0200, Jiri Kosina wrote:
> 3) there simply is a need for CRD process for the kernel (which pretty
> much by definition is not happening publicly). Currently, security@
> serves that purpose, so if you make that public, you have to
> instantiate some other process to deal with CRDs.
Can you expand the acronym "CRD".
- Ted
next prev parent reply other threads:[~2018-09-23 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 21:14 James Morris
2018-09-22 13:16 ` Dan Carpenter
2018-09-23 13:15 ` Laura Abbott
2018-09-23 13:20 ` Jiri Kosina
2018-09-23 18:34 ` Theodore Y. Ts'o [this message]
2018-09-23 18:54 ` Jiri Kosina
2018-09-24 9:21 ` Dan Carpenter
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=20180923183407.GA2774@thunk.org \
--to=tytso@mit.edu \
--cc=dan.carpenter@oracle.com \
--cc=jikos@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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