linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Martin Wege <martin.l.wege@gmail.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: SELinux-Support in Linux NFSv4.1 impl?
Date: Sun, 18 Feb 2024 08:54:56 -0500	[thread overview]
Message-ID: <2e4760a87e1fc6906562442c27933e830635a929.camel@kernel.org> (raw)
In-Reply-To: <CANH4o6O-Gcjc3eqiTd-KysZx-bpbzoh=CMTNixJ26cZQuRd=UQ@mail.gmail.com>

On Sat, 2024-02-17 at 14:37 +0100, Martin Wege wrote:
> On Wed, Feb 14, 2024 at 12:28 PM Jeff Layton <jlayton@kernel.org> wrote:
> > 
> > On Wed, 2024-02-14 at 10:46 +0100, Martin Wege wrote:
> > > Hello,
> > > 
> > > Does the Linux implementation server&client for NFSv4.1 support SELinux?
> > > 
> > > 
> > 
> > Labeled NFS is a NFSv4.2 feature. The Linux client and server do support
> 
> Is there documentation on how to set this up? Will this work if the
> root fs ('/') is NFSv4.2?
> 

There isn't much to set up. If you mount using NFSv4.2, the client and
server should negotiate using SELinux (assuming both are SELinux
enabled) and the SELinux contexts should (mostly) be projected across
the wire.

I've not tested it with nfsroot support, but I don't see why it wouldn't
work.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2024-02-18 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  9:46 SELinux-Support in Linux NFSv4.1 impl? Martin Wege
2024-02-14 11:28 ` Jeff Layton
2024-02-17 13:37   ` Martin Wege
2024-02-18 13:54     ` Jeff Layton [this message]
     [not found]       ` <CAENext6Zuv0pLgzp_vcBqdKmrH6Bg5GDV_hnUNOeFK2juoiJnw@mail.gmail.com>
2024-02-18 14:35         ` Jeff Layton
2024-02-26  7:30           ` Martin Wege
2024-11-21 10:46             ` Martin Wege
2024-11-27 18:16     ` Matt Kinni

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=2e4760a87e1fc6906562442c27933e830635a929.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=martin.l.wege@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 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 NNTP newsgroup(s).