All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: casey@schaufler-ca.com, labeled-nfs@linux-nfs.org, selinux@tycho.nsa.gov
Subject: Re: [Labeled-nfs] [PATCH 13/13] NFSD: Label change notification for NFSv4 Server
Date: Tue, 20 Nov 2007 09:48:27 +1100 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0711200923540.5484@us.intercode.com.au> (raw)
In-Reply-To: <1195509634.5327.16.camel@heimdal.trondhjem.org>

On Mon, 19 Nov 2007, Trond Myklebust wrote:

> This proposal, OTOH, will force the server to track all clients that
> access a labelled file, and to notify them all synchronously if ever a
> change is made. That can never scale if, say, you want to relabel the
> entire filesystem as SELinux appears wont to do.

There are further requirements for conveying volatile security state 
between the peers, such as: the current security context of the client, 
and the client's current explicit label for new files (if present).

A possible approach for dealing with all of these is to use a 
per-procedure OP which is prefixed in a similar manner to SEQUENCE, when 
security labeling is active.  It may be possible to optimize this at the 
server so that an updated file security label (or ineed the entire 
security OP) is only sent if required.


-- 
James Morris
<jmorris@namei.org>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

      parent reply	other threads:[~2007-11-19 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1195506545.5327.1.camel@heimdal.trondhjem.org>
2007-11-19 21:44 ` [Labeled-nfs] [PATCH 13/13] NFSD: Label change notification for NFSv4 Server Casey Schaufler
     [not found]   ` <1195509634.5327.16.camel@heimdal.trondhjem.org>
2007-11-19 22:48     ` James Morris [this message]

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=Xine.LNX.4.64.0711200923540.5484@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=casey@schaufler-ca.com \
    --cc=labeled-nfs@linux-nfs.org \
    --cc=selinux@tycho.nsa.gov \
    --cc=trond.myklebust@fys.uio.no \
    /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.