gocryptfs/tests, branch v1.5Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.52018-06-07T20:50:30+00:00main: accept -dev, -nodev, -suid, -nosuid, -exec, -noexec2018-06-07T20:50:30+00:00Jakob Unterwurzacher2018-06-07T20:50:30+00:00urn:sha1:53d6a9999dd0e4c31636d16179f284fff35a35d9
When mounted via /etc/fstab like this,
/a /b fuse.gocryptfs default 0 0
we always get extra options passed. As reported by @mahkoh
at https://github.com/rfjakob/gocryptfs/pull/233 :
mount passes `-o noexec` if `-o user` is set and `-o exec` is not set.
If both `-o user` and `-o exec` are set, it passes `-o exec`.
Make these options work, and in addtion, also make -suid and -rw
work the same way.
Reported-by: @mahkoh
main: make prefixOArgs errors testable2018-06-05T19:02:35+00:00Jakob Unterwurzacher2018-06-05T19:02:35+00:00urn:sha1:e29a81efc3df88b451a4a9464724a952d97b4115
By returning an error instead of calling os.Exit,
error cases can be tested easily. Error cases
were not tested until now.
xattr: use LGet/LSet etc2018-05-27T18:09:48+00:00Jakob Unterwurzacher2018-05-27T18:09:48+00:00urn:sha1:ae02ca1ded252262a5d727de9b9b4be278e60ba2
Support has been merged into the xattr package
( https://github.com/pkg/xattr/pull/29 ), use it.
tests: add "mv broken symlink" test2018-05-17T21:14:33+00:00Jakob Unterwurzacher2018-05-17T21:14:33+00:00urn:sha1:44caf21debd445623fb481827fae6fc8a5eb911d
This currently fails because we do not use llistxattr
yet.
xattr: return EOPNOTSUPP for unsupported attributes2018-05-15T21:00:47+00:00Jakob Unterwurzacher2018-05-15T21:00:47+00:00urn:sha1:7b0068180772b9dd7e0b00ca9e1b0f3ce39c9c23
mv is unhappy when we return EPERM when it tries to set
system.posix_acl_access:
mv: preserving permissions for ‘b/x’: Operation not permitted
Now we return EOPNOTSUPP like tmpfs does and mv seems happy.
fsck: update testcases with binary xattrs2018-05-10T21:26:00+00:00Jakob Unterwurzacher2018-05-10T21:18:16+00:00urn:sha1:f7a6f4d46858dcd049bcf671509bdf42e5d26d09xattr: optimize storage, store as binary instead of bae642018-05-10T21:25:49+00:00Bolshevik2018-05-07T20:01:36+00:00urn:sha1:a41ec2028cf2ad24eafb531d661ea1fe0f751f39
Values a binary-safe, there is no need to base64-encode them.
Old, base64-encoded values are supported transparently
on reading. Writing xattr values now always writes them binary.
tests: example_filesystems: create a private copy in /tmp2018-05-04T20:27:59+00:00Jakob Unterwurzacher2018-05-04T20:27:59+00:00urn:sha1:fc8fca04a8139de3683afb9c7c354dbbb151e490
The tests write to the example_filesystems folder, which
1) May leave your source tree in a modified state
2) Triggers test failures when the fsck tests run concurrently,
which happens on Travis CI every now and then.
Fix both problem by copying the example_filesystems folder
to a private location in /tmp.
tests: helpers: fix a few error reports2018-04-27T18:19:51+00:00Jakob Unterwurzacher2018-04-27T18:19:51+00:00urn:sha1:996d2f141b2c4f0cb9b8fbf66d06a2fb6e8cbaef
These were using stale err values.
Fix the easy golint warnings2018-04-08T18:26:25+00:00Jakob Unterwurzacher2018-04-08T18:24:29+00:00urn:sha1:bcc8378a2c07476a43c1fe316b79590177ded3d3
Reported by https://goreportcard.com/report/github.com/rfjakob/gocryptfs