* Re: [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP
[not found] ` <20120211200346.GA16870@albatros>
@ 2012-02-11 20:19 ` Joe Perches
2012-02-11 20:33 ` Vasiliy Kulikov
2012-02-15 0:49 ` Kees Cook
0 siblings, 2 replies; 3+ messages in thread
From: Joe Perches @ 2012-02-11 20:19 UTC (permalink / raw)
To: Vasiliy Kulikov
Cc: Will Drewry, linux-kernel, linux-fsdevel, linux-security-module, netdev
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP
2012-02-11 20:19 ` [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP Joe Perches
@ 2012-02-11 20:33 ` Vasiliy Kulikov
2012-02-15 0:49 ` Kees Cook
1 sibling, 0 replies; 3+ messages in thread
From: Vasiliy Kulikov @ 2012-02-11 20:33 UTC (permalink / raw)
To: Joe Perches
Cc: Will Drewry, linux-kernel, linux-fsdevel, linun-security-module,
netdev, kernel-hardening
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP
2012-02-11 20:19 ` [PATCH v7 4/8] seccomp: Add SECCOMP_RET_TRAP Joe Perches
2012-02-11 20:33 ` Vasiliy Kulikov
@ 2012-02-15 0:49 ` Kees Cook
1 sibling, 0 replies; 3+ messages in thread
From: Kees Cook @ 2012-02-15 0:49 UTC (permalink / raw)
To: Joe Perches
Cc: Vasiliy Kulikov, Will Drewry, linux-kernel, linux-fsdevel,
linux-security-module, netdev
On Sat, Feb 11, 2012 at 12:19:03PM -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?
FWIW, I like getting direct emails in addition to the mailing list emails.
-Kees
--
Kees Cook @outflux.net
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-15 0:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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
2012-02-15 0:49 ` Kees Cook
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).