From ca9e912a28b901387e1dbb85f6c531119f2d5ef2 Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Sat, 29 Feb 2020 19:58:08 +0100
Subject: 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
---
 internal/fusefrontend/xattr_linux.go | 10 ----------
 1 file changed, 10 deletions(-)

(limited to 'internal/fusefrontend/xattr_linux.go')

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
 }
-- 
cgit v1.2.3