From: Stephen Smalley <sds@tycho.nsa.gov>
To: zyxel <zyx1984@gmail.com>
Cc: selinux@tycho.nsa.gov, Dave Quigley <selinux@davequigley.com>
Subject: Re: labeled NFS
Date: Mon, 21 May 2012 08:27:47 -0400 [thread overview]
Message-ID: <1337603267.28413.7.camel@moss-pluto> (raw)
In-Reply-To: <CAHx7xgUSgC+NgtroN8CpUJCbRvwbmtXw8HuerTFbRRXbMW9nBg@mail.gmail.com>
On Mon, 2012-05-21 at 15:50 +0400, zyxel wrote:
> Hello.
> I have another question about labeled nfs.
>
> If both client and server have are patched to support labeled NFS and
> if on the client side policy is set to permissive and on server side
> policy is set to enforcing,
> we can access files on the server from the client without any
> restrictions.
> Is it correct behaviour?
I believe so, as the LNFS implementation only deals with object labeling
support for NFSv4. Conveying the client process security label to the
server (so that the server can enforce per-process access controls)
would be provided by another mechanism such as RPCSEC_GSSv3.
--
Stephen Smalley
National Security Agency
--
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.
next prev parent reply other threads:[~2012-05-21 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 11:50 labeled NFS zyxel
2012-05-21 12:27 ` Stephen Smalley [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-30 18:06 Labeled NFS Myklebust, Trond
2012-05-11 11:05 labeled NFS zyxel
2012-05-11 14:28 ` Casey Schaufler
2012-05-11 15:12 ` zyxel
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=1337603267.28413.7.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=selinux@davequigley.com \
--cc=selinux@tycho.nsa.gov \
--cc=zyx1984@gmail.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.