gocryptfs/internal/fusefrontend_reverse, branch v1.7-rc1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7-rc1 2019-01-04T19:11:45+00:00 fusefrontend_reverse: Fix redeclaration of 'entries' variable. 2019-01-04T19:11:45+00:00 Sebastian Lackner 2019-01-04T18:52:17+00:00 urn:sha1:117dc3f2cc83831a955838ac8ceaeb962b9c8827 Go version go1.10.7 linux/amd64 complains with: internal/fusefrontend_reverse/rfs.go:333: declaration of "entries" shadows declaration at internal/fusefrontend_reverse/rfs.go:327 reverse mode: -exclude: filter out excluded .name files 2019-01-04T16:59:00+00:00 Jakob Unterwurzacher 2019-01-04T16:59:00+00:00 urn:sha1:6b94f5ef51c92f471919e7542a0ce45b0859282f Fixes https://github.com/rfjakob/gocryptfs/issues/286 : While the actual file is properly excluded, the * .name file is still leaked in the directory listing: ``` drwxr-xr-x 2 sebastian sebastian 4,0K Dez 17 14:58 . drwxr-xr-x 7 sebastian sebastian 4,0K Dez 17 14:45 .. -r-------- 1 sebastian sebastian 408 Dez 17 14:56 gocryptfs.conf -r--r--r-- 1 sebastian sebastian 16 Dez 17 14:58 gocryptfs.diriv -r--r--r-- 1 sebastian sebastian 320 Dez 17 14:58 gocryptfs.longname.3vZ_r3eDPb1_fL3j5VA4rd_bcKWLKT9eaxOVIGK5HFA.name ``` reverse mode: fix "-exclude" in "-plaintextnames" dir listings 2019-01-04T16:36:06+00:00 Jakob Unterwurzacher 2019-01-04T16:34:21+00:00 urn:sha1:75a3e2c2eed3c19444b8aa131337757b7a05c7b7 Excluded files showed up in directory listing like this: drwxr-xr-x 2 sebastian sebastian 4,0K Dez 17 14:48 . drwxr-xr-x 7 sebastian sebastian 4,0K Dez 17 14:45 .. -????????? ? ? ? ? ? abcd -r-------- 1 sebastian sebastian 366 Dez 17 14:45 gocryptfs.conf Fixes https://github.com/rfjakob/gocryptfs/issues/285 syscallcompat: use O_PATH in OpenDirNofollow 2018-09-08T16:06:33+00:00 Jakob Unterwurzacher 2018-09-08T16:06:33+00:00 urn:sha1:930c37e03d5ff80e7cdc9f0ca2cd35d80a06d5c0 This fixes the "0100 directory" problem in reverse mode, and should be slightly faster. syscallcompat: untangle OpenNofollow and rename to OpenDirNofollow 2018-09-08T15:41:17+00:00 Jakob Unterwurzacher 2018-09-08T15:41:17+00:00 urn:sha1:9ec9d0c49cfbdc9ceba10d7534b77e527c0a3cdc The function used to do two things: 1) Walk the directory tree in a manner safe from symlink attacks 2) Open the final component in the mode requested by the caller This change drops (2), which was only used once, and lets the caller handle it. This simplifies the function and makes it fit for reuse in forward mode in openBackingPath(), and for using O_PATH on Linux. fusefrontend_reverse: reject excludes for the root directory "" 2018-08-15T10:28:29+00:00 Jakob Unterwurzacher 2018-08-15T10:28:29+00:00 urn:sha1:7a02f71fc2fc8fc104ad1538f417d1e93e73cf11 This is most likely a mistake by the user. Reject it. reverse mode: add --exclude option 2018-08-11T21:26:49+00:00 Jakob Unterwurzacher 2018-08-11T21:26:49+00:00 urn:sha1:ec2fdc19cf9358ae7ba09c528a5807b6b0760f9b https://github.com/rfjakob/gocryptfs/issues/235 darwin does not have PATH_MAX 2018-06-07T22:47:48+00:00 Jakob Unterwurzacher 2018-06-07T22:47:48+00:00 urn:sha1:bde7ba57b06eb46f8901454e12524a74a8c3b6e8 Define our own, with the value from Linux. fusefrontend[_reverse]: move crypto init up to caller 2018-02-18T10:21:58+00:00 Jakob Unterwurzacher 2018-02-17T15:26:35+00:00 urn:sha1:719693ec5dd1153318606f151915231d71ddfe0b Both fusefrontend and fusefrontend_reverse were doing essentially the same thing, move it into main's initFuseFrontend. A side-effect is that we have a reference to cryptocore in main, which will help with wiping the keys on exit (https://github.com/rfjakob/gocryptfs/issues/211). gccgo: replace syscall.NAME_MAX with unix.NAME_MAX 2018-02-01T22:50:11+00:00 Jakob Unterwurzacher 2018-02-01T22:46:02+00:00 urn:sha1:9f8d0d8e5734e3771b52c8a8784ef5a76b0f9ca8 For some reason the syscall.NAME_MAX constant does not exist on gccgo, and it does not hurt us to use unix.NAME_MAX instead. https://github.com/rfjakob/gocryptfs/issues/201