From: Martin Wege <martin.l.wege@gmail.com>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: SELinux-Support in Linux NFSv4.1 impl?
Date: Mon, 26 Feb 2024 08:30:00 +0100 [thread overview]
Message-ID: <CANH4o6OmdiGDUjQd25Mza_bZX6zq5Vw85cD9X4RexWSQqxY4NQ@mail.gmail.com> (raw)
In-Reply-To: <7e499dd1deafcf043229973968920947453d4eba.camel@kernel.org>
On Sun, Feb 18, 2024 at 3:35 PM Jeff Layton <jlayton@kernel.org> wrote:
>
> On Sun, 2024-02-18 at 16:16 +0200, Guy Keren wrote:
> > On Sun, Feb 18, 2024 at 3:55 PM Jeff Layton <jlayton@kernel.org> wrote:
> > >
> > > 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.
> >
> > Jeff - as far as i know, while it is possible for the client to
> > get/set the secure labels of files on the server - there is no way for
> > the client to tell the server which user is performing the specific
> > access operation - so the 'FULL MODE' of nfs4.2 security labels cannot
> > work - only the 'Limited Server Mode' mode (i.e. only the client
> > verifies the security labels - the server does not). please correct me
> > if i'm wrong.
> >
> >
>
> (re-cc'ing the mailing list...)
>
> That is correct. I'm not aware of anyone having implented "Full mode" as
> of yet anywhere.
>
> The Linux server is a "dumb" labeled NFS server that just projects the
> contexts to the clients and doesn't try to do any enforcement.
Is this documented somehere? "NFSv4.2 SELinux HOWTO" maybe?
Thanks,
Martin
next prev parent reply other threads:[~2024-02-26 7:30 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
[not found] ` <CAENext6Zuv0pLgzp_vcBqdKmrH6Bg5GDV_hnUNOeFK2juoiJnw@mail.gmail.com>
2024-02-18 14:35 ` Jeff Layton
2024-02-26 7:30 ` Martin Wege [this message]
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=CANH4o6OmdiGDUjQd25Mza_bZX6zq5Vw85cD9X4RexWSQqxY4NQ@mail.gmail.com \
--to=martin.l.wege@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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).