fusefrontend: drop xattr user namespace restriction

We used to restrict setting xattrs to the "user."
namespace. I don't see a real reason for this
anymore, and it causes trouble for users who are using
acls.

Tests will be added in the next commit.

https://github.com/rfjakob/gocryptfs/issues/453

1 files changed, 0 insertions, 12 deletions

diff --git a/internal/fusefrontend/xattr.go b/internal/fusefrontend/xattr.go
index 20e8db7..96a0372 100644
--- a/internal/fusefrontend/xattr.go
+++ b/internal/fusefrontend/xattr.go
@@ -27,10 +27,6 @@ func (fs *FS) GetXAttr(relPath string, attr string, context *fuse.Context) ([]by
 	if fs.isFiltered(relPath) {
 		return nil, fuse.EPERM
 	}
-	if disallowedXAttrName(attr) {
-		return nil, _EOPNOTSUPP
-	}
-
 	cAttr := fs.encryptXattrName(attr)
 
 	cData, status := fs.getXAttr(relPath, cAttr, context)
@@ -53,10 +49,6 @@ func (fs *FS) SetXAttr(relPath string, attr string, data []byte, flags int, cont
 	if fs.isFiltered(relPath) {
 		return fuse.EPERM
 	}
-	if disallowedXAttrName(attr) {
-		return _EOPNOTSUPP
-	}
-
 	flags = filterXattrSetFlags(flags)
 	cAttr := fs.encryptXattrName(attr)
 	cData := fs.encryptXattrValue(data)
@@ -70,10 +62,6 @@ func (fs *FS) RemoveXAttr(relPath string, attr string, context *fuse.Context) fu
 	if fs.isFiltered(relPath) {
 		return fuse.EPERM
 	}
-	if disallowedXAttrName(attr) {
-		return _EOPNOTSUPP
-	}
-
 	cAttr := fs.encryptXattrName(attr)
 	return fs.removeXAttr(relPath, cAttr, context)
 }