gocryptfs/tests/xattr, branch v2.0-beta2Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0-beta22020-07-12T11:40:21+00:00tests: don't crash on empty Flistxattr result2020-07-12T11:40:21+00:00Jakob Unterwurzacher2020-07-12T11:40:21+00:00urn:sha1:fd0e8aa869ec74917d669d42f0e0d3b2888237b9tests: test xattr acls2020-02-29T19:38:48+00:00Jakob Unterwurzacher2020-02-29T19:38:48+00:00urn:sha1:fdfaa849f8ea2fc6687aa13a7057b5088e3c65e5
Fixes https://github.com/rfjakob/gocryptfs/issues/453
tests: use /var/tmp by default2019-10-06T19:53:20+00:00Jakob Unterwurzacher2019-10-06T19:50:27+00:00urn:sha1:8c4429408716d9890a98a48c246d616dbfea7e31
On Fedora, /tmp is tmpfs, which behaves differently than ext4
(inode numbers are never reused, for example).
Use /var/tmp, which is ext4 on Fedora, to get a more realistic
test environment.
This also allows us to drop the xattr workaround.
fusefrontend: Allow to set/remove xattr on directory without read permission.2019-01-05T11:34:40+00:00Sebastian Lackner2019-01-05T03:33:50+00:00urn:sha1:5055f39bd534b1f13257f95ffdc28575b9b2e3ed
Setting/removing extended attributes on directories was partially fixed with
commit eff35e60b63331e3e10f921792baa10b236a721d. However, on most file systems
it is also possible to do these operations without read access (see tests).
Since we cannot open a write-access fd to a directory, we have to use the
/proc/self/fd trick (already used for ListXAttr) for the other operations aswell.
For simplicity, let's separate the Linux and Darwin code again (basically revert
commit f320b76fd189a363a34bffe981aa67ab97df3362), and always use the
/proc/self/fd trick on Linux. On Darwin we use the best-effort approach with
openBackingFile() as a fallback.
More discussion about the available options is available in
https://github.com/rfjakob/gocryptfs/issues/308.
fusefrontend: fix setting xattrs on directories2019-01-04T21:22:24+00:00Jakob Unterwurzacher2019-01-04T21:22:24+00:00urn:sha1:eff35e60b63331e3e10f921792baa10b236a721d
Directories cannot be opened read-write. Retry with RDONLY.
tests: xattr: set on 0200 file, list on 0000 file2019-01-02T19:45:55+00:00Jakob Unterwurzacher2019-01-02T19:45:55+00:00urn:sha1:d269c28d169cdf071acf57d283b756cde2b6437f
https://github.com/rfjakob/gocryptfs/issues/308
tests: better error message for TestBase64XattrRead2019-01-02T15:55:51+00:00Jakob Unterwurzacher2019-01-02T15:55:51+00:00urn:sha1:55a27a47dfb61cf553cf499802d614926b3b8a72
Make clear what we have and what we want.
fusefrontend: xattr: fix hang on FIFOs2019-01-01T15:24:25+00:00Jakob Unterwurzacher2018-11-12T21:22:10+00:00urn:sha1:60e7a0ca9f2a2bcf8a727f606db134d60e9a5e18
An Open() a fifo blocks until it is opened for writing.
This meant that xattr operations on FIFOs would block.
Pass O_NONBLOCK to fix that, and add a test.
fusefrontend: make GetXAttr() symlink-safe on Linux2019-01-01T15:24:25+00:00Jakob Unterwurzacher2018-11-11T16:43:48+00:00urn:sha1:2286372603f506cf719654a9901de0749c544b12
Uses the /proc/self/fd trick, which does not work
on Darwin.
tests: add Flistxattr/Fgetxattr/Fremovexattr tests2019-01-01T15:24:25+00:00Jakob Unterwurzacher2018-11-11T14:48:39+00:00urn:sha1:b97d7d1d33d1274c6872d899692a56bd4070a6d9
Test for the upcoming fd-based xattr support.