<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/internal/fusefrontend/xattr_linux_unit_test.go, branch LockSharedStorage_rebase2</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=LockSharedStorage_rebase2</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=LockSharedStorage_rebase2'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2020-02-29T19:12:43+00:00</updated>
<entry>
<title>fusefrontend: drop xattr user namespace restriction</title>
<updated>2020-02-29T19:12:43+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-02-29T18:58:08+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=ca9e912a28b901387e1dbb85f6c531119f2d5ef2'/>
<id>urn:sha1:ca9e912a28b901387e1dbb85f6c531119f2d5ef2</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Improved xattr handling on non-linux systems (#227)</title>
<updated>2018-04-17T18:33:04+00:00</updated>
<author>
<name>bolshevik</name>
</author>
<published>2018-04-17T18:33:04+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=12b32aa06c0475d60ee51b3753052ac2e4d09308'/>
<id>urn:sha1:12b32aa06c0475d60ee51b3753052ac2e4d09308</id>
<content type='text'>
* Fixed xattr filtering for MacOS. "system." and "user." prefixes are only relevant for Linux.
* Small cleanup and additional tests.</content>
</entry>
</feed>
