mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Kylene Jo Hall <kjhall@us.ibm.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	LSM ML <linux-security-module@vger.kernel.org>,
	Dave Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>,
	Serge Hallyn <sergeh@us.ibm.com>
Subject: Re: [PATCH 3/7] SLIM main patch
Date: Thu, 24 Aug 2006 10:31:44 +0200	[thread overview]
Message-ID: <1156408305.3014.38.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1156371603.6720.101.camel@localhost.localdomain>

On Wed, 2006-08-23 at 15:20 -0700, Kylene Jo Hall wrote:
> On Wed, 2006-08-23 at 16:41 -0400, Benjamin LaHaise wrote:
> > On Wed, Aug 23, 2006 at 01:35:56PM -0700, Kylene Jo Hall wrote:
> > > Example: The current process is running at the USER level and writing to
> > > a USER file in /home/user/.  The process then attempts to read an
> > > UNTRUSTED file.  The current process will become UNTRUSTED and the read
> > > allowed to proceed but first write access to all USER files is revoked
> > > including the ones it has open.
> > 
> > Don't threads share file tables?  What is preventing malicious code from 
> > starting another thread which continues writing to the file that the 
> > revoke attempt is made on?
> 
> Well if they do share file tables then revoking write access from the
> file in the file table will revoke access for all threads.  It looks
> like sharing or copying the file table is based on a flag to the clone
> call and we are looking into whether you could exploit that situation.


well there's many corner cases; like dup2(), or sending the fd over unix
domains (and having it pending there while the revoke happens, and later
accept it)....


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com


  reply	other threads:[~2006-08-24  8:32 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 [this message]
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
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=1156408305.3014.38.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --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=sergeh@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®