gocryptfs, branch v2.4.0Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v2.4.02023-06-10T14:31:49+00:00README: update changelog for v2.4.02023-06-10T14:31:49+00:00Jakob Unterwurzacher2023-06-10T14:31:49+00:00urn:sha1:8979cca43ea2ed15cf6ff577619298b9473d2882tests: add cluster test2023-05-30T07:43:45+00:00Jakob Unterwurzacher2023-05-30T07:43:45+00:00urn:sha1:3058b7978fd8dabd3e8565c9be816b1367bd196a
finds out what happens if multiple
gocryptfs mounts write to one file concurrently
(usually, nothing good).
This use case is relevant for HPC clusters.
fsstress-gocryptfs.bash: improve header comment2023-05-19T11:17:24+00:00Jakob Unterwurzacher2023-05-19T11:17:24+00:00urn:sha1:b725de5ec300aec208908c6a3bf5443cee7cfa81
I maybe should have noted that this is xfstests generic/013.
tests: TestDirectMount: check for default_permissions2023-05-18T08:14:21+00:00Jakob Unterwurzacher2023-05-18T08:14:21+00:00urn:sha1:c67454464aaabec7c594eeb84983287057ab4231fusefrontend: implement our own Access()2023-05-17T21:26:56+00:00Jakob Unterwurzacher2023-05-17T21:26:56+00:00urn:sha1:09954c4bdecf0ca6da65776f176dc934ffced2b0
Not having Access() means go-fuse emulates it by looking at Getattr().
This works fine most of the time, but breaks down on sshfs, where
sshfs-benchmark.bash shows this:
gocryptfs/tests$ ./sshfs-benchmark.bash nuetzlich.net
working directory: /tmp/sshfs-benchmark.bash.JQC
sshfs mounted: nuetzlich.net:/tmp -> sshfs.mnt
gocryptfs mounted: sshfs.mnt/sshfs-benchmark.bash.Wrz/gocryptfs.crypt -> gocryptfs.mnt
sshfs-benchmark.bash: sshfs gocryptfs-on-sshfs
git init 3.98 6.80
rsync 7.71 10.84
rm -R 4.30rm: descend into write-protected directory 'gocryptfs.mnt/git1'?
The go-fuse emulation gets it wrong here because sshfs reports
permissions but does not enforce them.
Implement it ourselves properly.
go.mod: add test dependency github.com/moby/sys/mountinfo2023-05-17T15:22:39+00:00Jakob Unterwurzacher2023-05-17T15:22:39+00:00urn:sha1:7d1e48d195b827ee00bfd0ab0421a395b1ec0ea7mount: set DirectMount: true2023-05-17T14:47:22+00:00Jakob Unterwurzacher2023-05-17T14:47:22+00:00urn:sha1:a40e9a8622b0d79ba0c18361104c47375ebb89a1
Attempt to directly call mount(2) before trying fusermount. This means we
can do without fusermount if running as root.
https://github.com/rfjakob/gocryptfs/issues/697
tests: TestDirectMount: also check dev, suid2023-05-17T14:08:49+00:00Jakob Unterwurzacher2023-05-17T14:08:49+00:00urn:sha1:8d3b992824072a3b487214812655a35fd28ee4dcmount: drop "max_read="2023-05-17T13:48:23+00:00Jakob Unterwurzacher2023-05-17T13:37:11+00:00urn:sha1:b4defa636b901d992165e2a828872dd410c48292
go-fuse now sets this internally.
Regression-tested in TestDirectMount.
mount: set FsName via go-fuse2023-05-17T13:38:35+00:00Jakob Unterwurzacher2023-05-17T13:35:01+00:00urn:sha1:199a74bc1ae49cdda486095b8daa8034510943a6
go-fuse now handles setting FsName, including DirectMount,
so use that instead of our own solution.
Regression-tested in TestDirectMount.