Features/LabeledNFS

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Comments and Discussion)
(How To Test)
Line 45: Line 45:
 
Do to a bug in nfs-utils:
 
Do to a bug in nfs-utils:
  
On the server you to start the server
+
* Server Side
 
     service nfs start  
 
     service nfs start  
 
Bring down the server  
 
Bring down the server  
Line 52: Line 52:
 
     echo "+4.2" > /proc/fs/nfsd/versions
 
     echo "+4.2" > /proc/fs/nfsd/versions
 
Then start the server again...  
 
Then start the server again...  
 
+
* Client Side
 +
    mount  -o v4.2 server:mntpoint localmountpoint
  
 
There are many different scenarios that have to be tested with this new functionality.
 
There are many different scenarios that have to be tested with this new functionality.

Revision as of 13:00, 16 July 2013

Contents

SELinux Labeled NFS Support

Summary

The Linux Kernel has grown support for passing SELinux labels between a client and server using NFS.

Owner

  • Email: <dwalsh@redhat.com>

Current status

  • Targeted release: [Fedora 20]
  • Last updated: Jul 15 2013
  • Percentage of completion: 90%


Detailed Description

We have always needed to treat NFS mounts with a single label usually something like nfs_t. Or at best allow an administrator to override the default with a label using the mount --context option. With this change we have lots of different Labels supported on an NFS share.

Benefit to Fedora

There are two huge benefits for Fedora, in that currently we can not differentiate different labels on a single NFS mount point. Applications like Secure Virtualization as launched by libvirt, can not set the label of an image file on an NFS share, so sVirt separation is severely weakened. Similarly if you setup home directories on an NFS share, then any confined application that needs to write a file in a home directory now can write any file on an NFS Share.

With labeled NFS this vulnerability goes away.

Scope

Turn on Labeled NFS in the Fedora Kernel, Fix any policy issues that arise because of this. I believe this is mainly a testing issue, and that the functionality is comeplet.

How To Test

Do to a bug in nfs-utils:

  • Server Side
   service nfs start 

Bring down the server

   service nfs stop

Set the version

   echo "+4.2" > /proc/fs/nfsd/versions

Then start the server again...

  • Client Side
   mount  -o v4.2 server:mntpoint localmountpoint

There are many different scenarios that have to be tested with this new functionality.

Basically with Labeled NFS we need to test with client and servers supporting LNFS and SELinux

SELinux Testing

  • SELinux Client LNFS - SELinux Server LNFS
  • SELinux Client LNFS - SELinux Server No LNFS
  • SELinux CLient LNFS - Server LNFS
  • SELinux CLient LNFS - Server No LNFS
  • Client LNFS - SELinux Server LNFS
  • Client LNFS - SELInux Server No LNFS
  • Client LNFS - Server LNFS
  • Client LNFS - Server no LNFS
  • Client no LNFS - SELinux Server LNFS
  • Client no LNFS - SELInux Server No LNFS
  • Client no LNFS - Server LNFS
  • Client no LNFS - Server no LNFS

Also need testing on three way. IE You need two clients that support SELinux CLient NFS and change the label on one client, and make sure the other client sees the change.

Contingency Plan

We can continue using what we always did, all clients labeled the same

Documentation

Release Notes

Comments and Discussion