gocryptfs/internal/fusefrontend_reverse, branch LockSharedStorage_rebase1Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=LockSharedStorage_rebase12024-11-11T21:33:07+00:00Report inode number for the root node2024-11-11T21:33:07+00:00Jakob Unterwurzacher2024-11-11T21:27:42+00:00urn:sha1:86891054ef2a5d1b0b59c7c140aae284e7c5bd87
Now that https://github.com/hanwen/go-fuse/issues/399 has
landed we can report an inode number for the root node.
Fixes https://github.com/rfjakob/gocryptfs/issues/580
reverse: fix import sorting in root_node.go2024-11-11T21:33:07+00:00Jakob Unterwurzacher2024-11-11T21:26:55+00:00urn:sha1:12c0f3a0bdd11444b8bf880af7c63ea7850391f2reverse: fix force_owner2024-08-23T20:32:46+00:00Jakob Unterwurzacher2024-08-23T20:32:46+00:00urn:sha1:f665be1178c72a4768e82bccdfa073a0cf309215
Fixes https://github.com/rfjakob/gocryptfs/issues/809
reverse: use incrementing inode number for gocryptfs.longname.*.name files2024-05-05T20:46:17+00:00Jakob Unterwurzacher2024-05-05T20:46:17+00:00urn:sha1:a38507978442f28ace42ec0003c4a2bf61cb4a91
ed0a12b7337c2d88c027329f64e73070da17d5b3 already fixed the kernel side,
now we also want the .name files to NOT appear hardlinked when just
looking at the inode number.
Relates-to: https://github.com/rfjakob/gocryptfs/issues/802
reverse: use unique generation number for all nodes2024-05-01T20:26:37+00:00Jakob Unterwurzacher2024-05-01T20:26:37+00:00urn:sha1:ed0a12b7337c2d88c027329f64e73070da17d5b3
We used to present gocryptfs.longname.*.name files for hardlinked
files as hardlinked to the kernel (same Node ID) which is wrong.
Fix this by using a unique generation number for all nodes, which
also fixes possible issues with inode reuse.
Basically what 1bc1db620b061aabf59469a5eb4fb60e3e1701a3 did
for forward mode with -sharedstorage.
Fixes https://github.com/rfjakob/gocryptfs/issues/802
make format2022-08-28T09:11:36+00:00Jakob Unterwurzacher2022-08-28T09:11:36+00:00urn:sha1:003a7fa2e53ac15d2c94a34102ae12b69b23c586Fix invalid -longnamemax for reverse mode2022-08-28T09:09:01+00:00NekoGirlSAIKOU2022-04-24T17:35:30+00:00urn:sha1:1bff80b46cf3cdd2d6934ebf905fca96dde7af97Fix reverse gocryptfs.conf access on macOS2022-04-02T13:15:04+00:00Val2022-03-31T18:41:36+00:00urn:sha1:c9e4e4f74150d2734496e90a4c442a17b79f52c1
Unlike the FUSE implementation on Linux, macFUSE doesn't cache the file
attributes from the `LOOKUP` call, so it calls `GETATTR` prior to
accessing a file.
In the case of the `VirtualConfNode` (reverse config file passthrough),
this resulted in the default `GETATTR` implementation returning an empty
result, ultimately resulting in a "permission denied" error.
14:44:14.095207 rx 3: GETATTR n2
14:44:14.095229 tx 3: OK, {tA=1s {M0100000 SZ=0 L=0 0:0 0 0:8954996 A 0.000000 M 0.000000 C 0.000000}}
14:44:14.099943 rx 4: ACCESS n2 {u=501 g=20 r}
14:44:14.099990 tx 4: 13=permission denied
By impementing `Getattr` (from `fs.NodeGetattrer`) on `VirtualConfNode`
this solves the issue.
inomap: deterministically set root device2021-09-10T15:17:16+00:00Jakob Unterwurzacher2021-09-10T15:17:16+00:00urn:sha1:c9b825c58a9f996379108926754513bca03bb306
We used to have "first Translate() wins". This is not deterministic,
as the LOOKUP for the root directory does not seem to reach us, so
the first user LOOKUP would win, which may be on a mountpoint.
go mod: declare module version v22021-08-23T13:05:15+00:00Jakob Unterwurzacher2021-08-23T13:05:15+00:00urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858
Our git version is v2+ for some time now, but go.mod
still declared v1. Hopefully making both match makes
https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work.
All the import paths have been fixed like this:
find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/%