From: "Serge E. Hallyn" <serge@hallyn.com>
To: Christian Stroetmann <stroetmann@ontolinux.com>
Cc: Kees Cook <kees.cook@canonical.com>,
James Morris <jmorris@namei.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Preview of changes to the Security susbystem for 2.6.36
Date: Mon, 2 Aug 2010 13:08:59 -0500 [thread overview]
Message-ID: <20100802180859.GA29948@hallyn.com> (raw)
In-Reply-To: <4C569BCA.3050603@ontolinux.com>
Quoting Christian Stroetmann (stroetmann@ontolinux.com):
> Aloha James, Aloha Kees;
> Ont the 02.08.2010 08:57, Kees Cook wrote:
> >On Mon, Aug 02, 2010 at 04:41:08PM +1000, James Morris wrote:
> >>On Sun, 1 Aug 2010, Kees Cook wrote:
> >>>Well, at least I'll have something for my summit presentation again.
> >>>
> >>>On the other hand, it's rather hard for me to defend against a private NAK.
>
> A private NAK against a company's developer's OK
> Where is the difference private and company? I thought that it
> doesn't matter who and what a developer is, and where she/he comes
> from.
That's not what private means in this case. A private nak is one made
in a private email, so that the list - and the submitter - can't see the
rationale. It is problematic because it doesn't really allow the other
party to address the objection.
(No big deal - Christoph has since responded in public.)
-serge
next prev parent reply other threads:[~2010-08-02 18:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 8:59 Preview of changes to the Security susbystem for 2.6.36 James Morris
2010-08-02 2:18 ` James Morris
2010-08-02 6:32 ` Kees Cook
2010-08-02 6:41 ` James Morris
2010-08-02 6:57 ` Kees Cook
2010-08-02 10:19 ` Christian Stroetmann
2010-08-02 16:36 ` Kees Cook
2010-08-02 17:33 ` Christian Stroetmann
2010-08-03 17:07 ` Kees Cook
2010-08-02 18:08 ` Serge E. Hallyn [this message]
2010-08-02 18:50 ` Christian Stroetmann
2010-08-02 12:24 ` Christoph Hellwig
2010-08-02 16:59 ` Kees Cook
2010-08-02 18:34 ` David P. Quigley
2010-08-03 17:04 ` Kees Cook
2010-08-02 18:51 ` Valdis.Kletnieks
2010-08-03 16:50 ` Kees Cook
2010-08-03 21:38 ` Valdis.Kletnieks
2010-08-03 22:34 ` Kees Cook
2010-08-04 2:07 ` Valdis.Kletnieks
2010-08-04 2:55 ` Kees Cook
2010-08-04 3:54 ` Tetsuo Handa
2010-08-04 6:18 ` Valdis.Kletnieks
2010-08-04 7:00 ` Tetsuo Handa
2010-08-04 16:23 ` Valdis.Kletnieks
2010-08-04 12:21 ` Christian Stroetmann
2010-08-03 21:52 ` Christian Stroetmann
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=20100802180859.GA29948@hallyn.com \
--to=serge@hallyn.com \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stroetmann@ontolinux.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.