On Fri, 2020-03-06 at 17:01 -0500, Scott Mayhew wrote: > On Wed, 04 Mar 2020, Stephen Smalley wrote: > > > On Wed, Mar 4, 2020 at 9:37 AM Scott Mayhew <smayhew@xxxxxxxxxx> > > wrote: > > > On Wed, 04 Mar 2020, Richard Haines wrote: > > > > I built and tested this patch on selinux-next (note that the > > > > NFS module > > > > is a few patches behind). > > > > The unlabeled problem is solved, however using: > > > > > > > > mount -t nfs -o > > > > vers=4.2,rootcontext=system_u:object_r:test_filesystem_file_t:s > > > > 0 > > > > localhost:$TESTDIR /mnt/selinux-testsuite > > > > > > > > I get the message: > > > > mount.nfs: an incorrect mount option was specified > > > > with a log entry: > > > > SELinux: mount invalid. Same superblock, different > > > > security > > > > settings for (dev 0:42, type nfs) > > > > > > > > If I use "fscontext=" instead then works okay. Using no context > > > > option > > > > also works. I guess the rootcontext= option should still work > > > > ??? > > > > > > Thanks for testing. It definitely wasn't my intention to break > > > anything, so I'll look into it. > > > > I'm not sure that rootcontext= should be supported or is > > supportable > > over labeled NFS. > > Should rootcontext= be supported for NFS versions < 4.2? If not then > maybe it that option should be rejected for nfs and nfs4 fstypes in > selinux_set_mnt_opts(). > > > It's primary use case is to allow assigning a specific context > > other > > than the default policy-defined one > > to the root directory for filesystems that support labeling but > > don't > > have existing labels on their root > > directories, e.g. tmpfs mounts. Even if we set the rootcontext > > based > > on rootcontext= during mount(2), > > it would likely get overridden by subsequent attribute fetches from > > the server I would think (e.g. it probably > > already switches to the context from the server after 30 seconds or > > Yes, that's what happens. If we wanted to retain that behavior > moving > forward, then we need to avoid calling nfs_setsecurity() for the root > inode when the rootcontext= option was used. To do that, I think > we'd > need to add a flag that could be passed back to NFS via the > set_kern_flags parameter of selinux_set_mnt_opts(). > > > so?). As long as the separate context= option > > continues to work correctly on NFS, I'm not overly concerned about > > this. > > Yep, the context= option still works. > > I should note that we are getting similar errors though when trying > > to > > specify any context-related > > mount options on NFS via the new fsconfig(2) system call, see > > https://github.com/SELinuxProject/selinux-kernel/issues/49 I've done further testing and found that with this patch the fsconfig(2) problem is also resolved for nfs (provided the rootcontext is not specified). > > I don't know if this change in when security_sb_set_mnt_opts() will > > alter that situation any. > > > > Also, FYI, we have recently made it possible to run the > > selinux-testsuite without errors within a labeled NFS > > mount. If you clone > > https://github.com/SELinuxProject/selinux-testsuite/ and follow the > > README.md > > instructions including the NFS section and run ./tools/nfs.sh, it > > will > > export and mount the testsuite directory > > via labeled NFS over loopback and run all tests that can be > > supported > > over NFS, and then runs a few specific > > tests for context= mount options (but not the other mount options > > at > > present). It still needs some further > > enhancements as per > > https://github.com/SELinuxProject/selinux-testsuite/issues/32#issuecomment-582992492 > > but it at least provides some degree of regression testing. Could you describe how I could test these, also are there any other SELinux tests that may be useful (with howto's). I'm almost ready to post another set of RFC test patches, but can add more. > > Thanks. I ran this a few times and aside from an exportfs bug > everything passed. I'll be sure to run this in the future too. > > -Scott >
