Linux-NFS Archive mirror
 help / color / mirror / Atom feed
From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: "selinux@vger.kernel.org" <selinux@vger.kernel.org>
Cc: "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: nfs client uses different MAC policy or model
Date: Thu, 14 Mar 2024 23:49:53 +0000	[thread overview]
Message-ID: <ZfONIThp2RIfmu1O@goliath> (raw)


Hi,

It seems there is/was a problem using NFS security labels where the server and client use
different MAC policy or model. 

I was reading this page,

http://www.selinuxproject.org/page/Labeled_NFS/TODO#Label_Translation_Framework

It seems like this problem was known in 2009 when this page was written. Is
there a way to accomplish having extended attributes shared over NFS to a client
with different selinux policies ?

Maybe it's possible to allow the client to write local file context without
writing that down to the remote filesystem.

Thanks,
Daniel

             reply	other threads:[~2024-03-14 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 23:49 Daniel Walker (danielwa) [this message]
2024-03-15 15:47 ` nfs client uses different MAC policy or model Jeff Layton
2024-03-15 23:09   ` Daniel Walker (danielwa)

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=ZfONIThp2RIfmu1O@goliath \
    --to=danielwa@cisco.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=selinux@vger.kernel.org \
    --cc=xe-linux-external@cisco.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).