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_unit_test.go | 13 -------------
 1 file changed, 13 deletions(-)
 delete mode 100644 internal/fusefrontend/xattr_linux_unit_test.go

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

diff --git a/internal/fusefrontend/xattr_linux_unit_test.go b/internal/fusefrontend/xattr_linux_unit_test.go
deleted file mode 100644
index 5fea58b..0000000
--- a/internal/fusefrontend/xattr_linux_unit_test.go
+++ /dev/null
@@ -1,13 +0,0 @@
-// +build linux
-
-package fusefrontend
-
-import (
-	"testing"
-)
-
-func TestDisallowedLinuxAttributes(t *testing.T) {
-	if !disallowedXAttrName("xxxx") {
-		t.Fatalf("Names that don't start with 'user.' should fail")
-	}
-}
-- 
cgit v1.2.3