aboutsummaryrefslogtreecommitdiff
path: root/internal/fusefrontend/xattr_linux.go
diff options
context:
space:
mode:
authorJakob Unterwurzacher2020-02-29 19:58:08 +0100
committerJakob Unterwurzacher2020-02-29 20:12:43 +0100
commitca9e912a28b901387e1dbb85f6c531119f2d5ef2 (patch)
tree67fe7a623652911b524c36741f8319297f568caa /internal/fusefrontend/xattr_linux.go
parent9ec042f2f62bc95154d6c8b3215a2e7853f8f5c6 (diff)
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
Diffstat (limited to 'internal/fusefrontend/xattr_linux.go')
-rw-r--r--internal/fusefrontend/xattr_linux.go10
1 files changed, 0 insertions, 10 deletions
diff --git a/internal/fusefrontend/xattr_linux.go b/internal/fusefrontend/xattr_linux.go
index 3a64412..b43dfee 100644
--- a/internal/fusefrontend/xattr_linux.go
+++ b/internal/fusefrontend/xattr_linux.go
@@ -5,7 +5,6 @@ package fusefrontend
import (
"fmt"
- "strings"
"syscall"
"golang.org/x/sys/unix"
@@ -15,15 +14,6 @@ import (
"github.com/rfjakob/gocryptfs/internal/syscallcompat"
)
-// Only allow the "user" namespace, block "trusted" and "security", as
-// these may be interpreted by the system, and we don't want to cause
-// trouble with our encrypted garbage.
-const xattrUserPrefix = "user."
-
-func disallowedXAttrName(attr string) bool {
- return !strings.HasPrefix(attr, xattrUserPrefix)
-}
-
func filterXattrSetFlags(flags int) int {
return flags
}