From: "Serge E. Hallyn" <sergeh@us.ibm.com>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: serue@us.ibm.com, Serge E Hallyn <sergeh@us.ibm.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
kjhall@us.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>,
LSM ML <linux-security-module@vger.kernel.org>,
David Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH 3/7] SLIM main patch
Date: Thu, 24 Aug 2006 09:16:57 -0500 [thread overview]
Message-ID: <20060824141657.GC32764@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20060824140043.GL28594@kvack.org>
Quoting Benjamin LaHaise (bcrl@kvack.org):
> On Thu, Aug 24, 2006 at 08:58:03AM -0500, Serge E. Hallyn wrote:
> > Still not certain this is needed. If you were able to write data to a
> > pipe, then even though data may be in the buffer, the other end
> > shouldn't be able to read it if it's own level were changed.
>
> Then what is the benefit of the supposed revoke if it can be trivially
> bypassed?
How is it being bypassed?
If it can be shown how what is there is insufficient, then it'll have to
be fixed. I'm just not seeing it yet.
> Security has not been improved. It is better not to provide
> a supposed feature than to offer it up so riddled with holes as to make
> it pointless.
Some would say it's better to show what you've got, let others point out
the faults, and fix them. How else will anything ever get done...
-serge
next prev parent reply other threads:[~2006-08-24 14:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 19:05 Kylene Jo Hall
2006-08-23 19:27 ` Benjamin LaHaise
2006-08-23 20:35 ` Kylene Jo Hall
2006-08-23 20:41 ` Benjamin LaHaise
2006-08-23 22:20 ` Kylene Jo Hall
2006-08-24 8:31 ` Arjan van de Ven
2006-08-24 11:26 ` Alan Cox
2006-08-24 13:32 ` Serge E. Hallyn
2006-08-24 13:37 ` Benjamin LaHaise
2006-08-24 13:58 ` Serge E. Hallyn
2006-08-24 14:00 ` Benjamin LaHaise
2006-08-24 14:16 ` Serge E. Hallyn [this message]
2006-08-24 14:15 ` Alan Cox
2006-08-24 15:23 ` Serge E. Hallyn
2006-08-24 17:05 ` Alan Cox
2006-08-24 17:34 ` David Safford
2006-08-24 19:16 ` Serge E. Hallyn
2006-08-24 20:21 ` David Safford
2006-08-24 20:41 ` Mimi Zohar
2006-08-24 22:13 ` Alan Cox
2006-09-12 17:57 Kylene Jo Hall
2006-09-14 23:52 ` Andrew Morton
2006-09-15 16:57 ` Kylene Jo Hall
2006-09-26 18:44 ` Stephen Smalley
2006-10-19 20:48 ` Kylene Jo Hall
2006-10-20 15:32 ` Stephen Smalley
2006-10-20 17:58 ` Stephen Smalley
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=20060824141657.GC32764@sergelap.austin.ibm.com \
--to=sergeh@us.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@us.ibm.com \
--cc=serue@us.ibm.com \
--cc=zohar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®