Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7.1 2019-03-26T19:56:37+00:00 2019-03-26T19:56:37+00:00 Eduardo M KALINOWSKI 2019-02-16T20:55:54+00:00 urn:sha1:3bc100aeb3f0763f78c8b3a70165b9f8aaa52db5 This adds support for gitignore-like wildcards and exclude patters in reverse mode. It (somewhat) fixes #273: no regexp support, but the syntax should be powerful enough to satisfy most needs. Also, since adding a lot of --exclude options can be tedious, it adds the --exclude-from option to read patterns from a file (or files). 2019-01-20T12:10:59+00:00 Jakob Unterwurzacher 2019-01-20T12:10:59+00:00 urn:sha1:3d6b2685fb926b40b4eb528a8cbdc3871444d492 Breaks mounting on MacOS: unix.Faccessat on Darwin does NOT (yet) support AT_SYMLINK_NOFOLLOW. See d44fe89ba4f3252c5bd00c4f7730197732f2a26a . This reverts commit 0805a63df1b5f915b228727f6074c2506922d0ad. 2019-01-20T11:59:59+00:00 Jakob Unterwurzacher 2019-01-20T11:59:59+00:00 urn:sha1:0805a63df1b5f915b228727f6074c2506922d0ad unix.Faccessat has added support for AT_SYMLINK_NOFOLLOW in July 2018, https://github.com/golang/sys/commit/bd9dbc187b6e1dacfdd2722a87e83093c2d7bd6e#diff-341484dbbe3180cd7a31ef2ad2d679b6 which means we no longer need our own helper. Closes https://github.com/rfjakob/gocryptfs/issues/347 2019-01-04T16:57:57+00:00 Jakob Unterwurzacher 2019-01-04T16:57:57+00:00 urn:sha1:58f62ada465c4ecbdb9a62a08968bebe37f02b7d Currently fails, will be fixed in the next commit. https://github.com/rfjakob/gocryptfs/issues/286 2019-01-02T00:09:09+00:00 Jakob Unterwurzacher 2019-01-02T00:09:09+00:00 urn:sha1:772afa93f98aa77959995e42564b898057c59b87 Give the gocryptfs process one extra millisecond to close files. Allows us to drop several other sleeps. UnmountErr now really returns an error when it detects an fd leak instead of just printing a message. 2019-01-01T23:09:17+00:00 Jakob Unterwurzacher 2019-01-01T21:54:41+00:00 urn:sha1:035b3367b7a447adc5e4c1ed96706f911c08c9f8 2018-12-27T14:19:55+00:00 Sebastian Lackner 2018-12-27T11:03:00+00:00 urn:sha1:874eaf9734cc10940e08f7b043652449e1e220b5 Mostly detected with the 'codespell' utility, but also includes some manual grammar fixes. 2018-10-10T20:40:55+00:00 Jakob Unterwurzacher 2018-10-10T20:38:22+00:00 urn:sha1:4f2feb1be7530d4fca7061b89d61f3ffc5761a0b Retry with length 1000 if length 4000 fails, which should work on all filesystems. Failure was: --- FAIL: TestTooLongSymlink (0.00s) correctness_test.go:198: symlink xxx[...]xxxx /tmp/xfs.mnt/gocryptfs-test-parent/549823072/365091391/TooLongSymlink: file name too long https://github.com/rfjakob/gocryptfs/issues/267 2018-09-08T17:27:33+00:00 Jakob Unterwurzacher 2018-09-08T17:27:33+00:00 urn:sha1:e8d8ae54d3b852d1d35b6db81d4a0beb57fbdce1 Rename openBackingPath to openBackingDir and use OpenDirNofollow to be safe against symlink races. Note that openBackingDir is not used in several important code paths like Create(). But it is used in Unlink, and the performance impact in the RM benchmark to be acceptable: Before $ ./benchmark.bash Testing gocryptfs at /tmp/benchmark.bash.bYO: gocryptfs v1.6-12-g930c37e-dirty; go-fuse v20170619-49-gb11e293; 2018-09-08 go1.10.3 WRITE: 262144000 bytes (262 MB, 250 MiB) copied, 1.07979 s, 243 MB/s READ: 262144000 bytes (262 MB, 250 MiB) copied, 0.882413 s, 297 MB/s UNTAR: 16.703 MD5: 7.606 LS: 1.349 RM: 3.237 After $ ./benchmark.bash Testing gocryptfs at /tmp/benchmark.bash.jK3: gocryptfs v1.6-13-g84d6faf-dirty; go-fuse v20170619-49-gb11e293; 2018-09-08 go1.10.3 WRITE: 262144000 bytes (262 MB, 250 MiB) copied, 1.06261 s, 247 MB/s READ: 262144000 bytes (262 MB, 250 MiB) copied, 0.947228 s, 277 MB/s UNTAR: 17.197 MD5: 7.540 LS: 1.364 RM: 3.410 2018-09-08T16:19:53+00:00 Jakob Unterwurzacher 2018-09-08T16:19:53+00:00 urn:sha1:84d6fafeca8f1d7b1b631a56fc3dc47016c4ba31 Go 1.7 does not have t.Name() yet.