• J. Bruce Fields's avatar
    nfsd: opt in to labeled nfs per export · 32ddd944
    J. Bruce Fields authored
    
    
    Currently turning on NFSv4.2 results in 4.2 clients suddenly seeing the
    individual file labels as they're set on the server.  This is not what
    they've previously seen, and not appropriate in may cases.  (In
    particular, if clients have heterogenous security policies then one
    client's labels may not even make sense to another.)  Labeled NFS should
    be opted in only in those cases when the administrator knows it makes
    sense.
    
    It's helpful to be able to turn 4.2 on by default, and otherwise the
    protocol upgrade seems free of regressions.  So, default labeled NFS to
    off and provide an export flag to reenable it.
    
    Users wanting labeled NFS support on an export will henceforth need to:
    
    	- make sure 4.2 support is enabled on client and server (as
    	  before), and
    	- upgrade the server nfs-utils to a version supporting the new
    	  "security_label" export flag.
    	- set that "security_label" flag on the export.
    
    This is commit may be seen as a regression to anyone currently depending
    on security labels.  We believe those cases are currently rare.
    
    Reported-by: default avatar <tibbs@math.uh.edu>
    Signed-off-by: default avatarJ. Bruce Fields <bfields@redhat.com>
    32ddd944