From: Vasiliy Kulikov <segoon@openwall.com>
To: Joe Perches <joe@perches.com>
Cc: Will Drewry <wad@chromium.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linun-security-module@vger.kernel.org, netdev@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP
Date: Sun, 12 Feb 2012 00:33:09 +0400 [thread overview]
Message-ID: <20120211203309.GA18093@albatros> (raw)
In-Reply-To: <1328991543.11026.8.camel@joe2Laptop>
On Sat, Feb 11, 2012 at 12:19 -0800, Joe Perches wrote:
> On Sun, 2012-02-12 at 00:03 +0400, Vasiliy Kulikov wrote:
> > On Sat, Feb 11, 2012 at 13:30 -0600, Will Drewry wrote:
> > > (As a side note, I realize the CC list has ballooned. In the next
> > > rev, I'll pare it down to active participants and the appropriate
> > > lists and not just the get_maintainers.pl output!)
> > Add kernel-hardening to CC and remove me and Kees ;)
>
> Should that list be added to MAINTAINERS or
> Documentation/ somewhere?
Probably yes, but we haven't fully agreed on what are the formal
criterias of k-h posting. Currently these are either discussion of
not-yet-merged security features or general security problems of Linux.
I guess we should more clearly state the role of k-h to place k-h in
MAINTAINERS.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2012-02-11 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328935151-6908-1-git-send-email-wad@chromium.org>
[not found] ` <1328935151-6908-5-git-send-email-wad@chromium.org>
[not found] ` <CAObL_7FJ=a-X0UuVuK1p338nAVCes4H8PTe2ji5dOLhrtSaKHQ@mail.gmail.com>
[not found] ` <CABqD9hYipmC1Dcx6+VrDM04ik5ysfw0GCypEzdFDBfh5B24jtA@mail.gmail.com>
[not found] ` <20120211200346.GA16870@albatros>
2012-02-11 20:19 ` [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP Joe Perches
2012-02-11 20:33 ` Vasiliy Kulikov [this message]
2012-02-15 0:49 ` Kees Cook
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=20120211203309.GA18093@albatros \
--to=segoon@openwall.com \
--cc=joe@perches.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linun-security-module@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).