Age | Commit message (Collapse) | Author | |
---|---|---|---|
2024-05-05 | reverse: use incrementing inode number for gocryptfs.longname.*.name files | Jakob Unterwurzacher | |
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 | |||
2024-05-05 | tests: reverse: deduplicate findInum / findIno | Jakob Unterwurzacher | |
2022-12-29 | make format | Jakob Unterwurzacher | |
Run "make format" using go version go1.19.4 linux/amd64 | |||
2021-08-20 | -deterministic-names: implement for reverse mode, too | Jakob Unterwurzacher | |
2020-08-15 | v2api/reverse: finish -exclude | Jakob Unterwurzacher | |
Tests pass now. | |||
2020-05-03 | fusefrontend_reverse: use inomap for inode number translation | Jakob Unterwurzacher | |
Gets rid of static inode number value limitations. Fixes https://github.com/rfjakob/gocryptfs/issues/457 | |||
2020-05-03 | tests: reverse: add inode mapping test (TestVirtualFileIno) | Jakob Unterwurzacher | |
Verify that virtual files get assigned inode numbers we expect. |