From: Anthony Messina <amessina@messinet.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Issue with SELinux Labeled NFS
Date: Tue, 11 Mar 2014 13:41:49 -0500 [thread overview]
Message-ID: <2308691.6kaIE5X6fN@linux-ws1.messinet.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
I've begun testing out the labeled NFSv4.2 features with good success with
only one exception so far. I have several workstations that use NFSv4.2
mounted /home directories. I've been able to remove the SELinux boolean
requirement for 'use_nfs_home_dirs', however, on *one* of these workstations,
the /home directory is labeled 'unlabeled_t' after boot when it should be
labeled with 'home_root_t'. This problem causes failures, as you can imagine.
I mount the filesystem on all of the workstations in the same manner:
# /etc/fstab
...
server.com:/home /home nfs rw,minorversion=2,sec=krb5p,x-systemd.automount 0 0
Yet the issue occurs on only *one* workstation. If I manually issue
chcon -t home_root_t /home
then I am able to login and use the system without issue.
All of the servers and workstations are using
kernel-3.13.6-200.fc20.x86_64
nfs-utils-1.2.9-3.0.fc20.x86_64
I realize this is not the SELinux mailing list, but I was wondering if anyone
had any pointers on how to investigate this issue. The workstations are all
nearly identical in configuration with the exception of a few user-based
differences such as GnuCash on one, but not the other, etc.
Thanks for your guidance. -A
--
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2014-03-11 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 18:41 Anthony Messina [this message]
2014-03-22 6:43 ` Issue with SELinux Labeled NFS Anthony Messina
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=2308691.6kaIE5X6fN@linux-ws1.messinet.com \
--to=amessina@messinet.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).