gocryptfs/internal, branch v1.5Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.52018-06-12T21:05:53+00:00xattr: return EOPNOTSUPP instead of ENODATA in GetXattr2018-06-12T21:05:53+00:00Jakob Unterwurzacher2018-06-12T19:07:00+00:00urn:sha1:bfa50517e9b0b3afe98084cc9ba105caba45b540
Reading system.posix_acl_access and system.posix_acl_default
should return EOPNOTSUPP to inform user-space that we do not
support ACLs.
xftestest essientially does
chacl -l | grep "Operation not supported"
to determine if the filesystem supports ACLs, and used to
wrongly believe that gocryptfs does.
darwin does not have PATH_MAX2018-06-07T22:47:48+00:00Jakob Unterwurzacher2018-06-07T22:47:48+00:00urn:sha1:bde7ba57b06eb46f8901454e12524a74a8c3b6e8
Define our own, with the value from Linux.
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.
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.
xattr: 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.
stupidgcm: return error on too short input instead of panicing2018-05-10T21:00:02+00:00Jakob Unterwurzacher2018-05-10T20:44:03+00:00urn:sha1:a276321dea04eaa0cfc80c56e8faca4b8ded0b7a
This is what Go GCM does as well.
xattr: added passing of a "flags" parameter2018-05-07T19:45:40+00:00Bolshevik2018-05-01T16:46:51+00:00urn:sha1:5ccc06d5cb321b1400e33a7d0819bf617c52600d
Pass the "flags" parameter to the lower layer syscall.
This makes Apple applications being able to successfully save data.
fusefrontend: xattr: return ENOSYS on unsupported flags2018-05-01T21:30:53+00:00Jakob Unterwurzacher2018-05-01T21:30:53+00:00urn:sha1:fe3890688a693fbfa900e32b05e10861fa4167ba
We previously returned EPERM to prevent the kernel from
blacklisting our xattr support once we get an unsupported
flag, but this causes lots of trouble on MacOS:
Cannot save files from GUI apps, see
https://github.com/rfjakob/gocryptfs/issues/229
Returning ENOSYS triggers the dotfiles fallback on MacOS
and fixes the issue.
Improved xattr handling on non-linux systems (#227)2018-04-17T18:33:04+00:00bolshevik2018-04-17T18:33:04+00:00urn:sha1:12b32aa06c0475d60ee51b3753052ac2e4d09308
* Fixed xattr filtering for MacOS. "system." and "user." prefixes are only relevant for Linux.
* Small cleanup and additional tests.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