gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2018-04-02	fsck: clean up log output	Jakob Unterwurzacher
	Make sure we get only 1 warning output per problem. Also, add new corruption types to broken_fs_v1.4.
2018-03-05	tests: fix a few fd leaks	Jakob Unterwurzacher
	We relied on the finalizer to close a few fds. For some reason, this did not cause problems on Linux, but on MacOS, it causes unmount failures: umount(/private/tmp/gocryptfs-test-parent/194654785/default-plain): Resource busy -- try 'diskutil unmount'
2017-08-10	tests: add diriv cache race test	Jakob Unterwurzacher
	Passes.
2017-07-11	fusefronted: enable writing to write-only files	Jakob Unterwurzacher
	Due to RMW, we always need read permissions on the backing file. This is a problem if the file permissions do not allow reading (i.e. 0200 permissions). This patch works around that problem by chmod'ing the file, obtaining a fd, and chmod'ing it back. Test included. Issue reported at: https://github.com/rfjakob/gocryptfs/issues/125
2017-05-07	fusefrontend: implement path decryption via ctlsock	Jakob Unterwurzacher
	Closes https://github.com/rfjakob/gocryptfs/issues/84 .
2017-05-01	tests: add TestXfs124	Jakob Unterwurzacher
	This test reproduces the problem xfstests generic/124 uncovered. The warning itself is harmless, but we should either (1) add locking so that this cannot happen anymore or (2) drop the warning. Currently fails: $ go test -v === RUN Test1980Tar --- PASS: Test1980Tar (0.00s) === RUN TestCtlSock --- PASS: TestCtlSock (0.10s) === RUN TestOpenTruncateRead --- PASS: TestOpenTruncateRead (0.00s) === RUN TestWORead --- PASS: TestWORead (0.00s) === RUN TestXfs124 cipherSize 18 == header size: interrupted write? -wpanic turns this warning into a panic: cipherSize 18 == header size: interrupted write?
2017-05-01	fusefrontend: drop writeOnly flag	Jakob Unterwurzacher
	We do not have to track the writeOnly status because the kernel will not forward read requests on a write-only FD to us anyway. I have verified this behavoir manually on a 4.10.8 kernel and also added a testcase.
2017-02-12	tests: ctlsock: check warning for non-canonical paths	Jakob Unterwurzacher

2016-12-10	ctlsock: sanitize paths before passing them to the backend	Jakob Unterwurzacher
	You used to be able to crash gocryptfs by passing "/foo" of "foo/" to the ctlsock. Fixes https://github.com/rfjakob/gocryptfs/issues/66
2016-11-17	tests: add OpenTruncateRead test	Jakob Unterwurzacher
	This is a regression test for the issue that was fixed by the last commit.
2016-11-10	ctlsock: implement EncryptPath for reverse mode, add tests	Jakob Unterwurzacher

2016-11-10	ctlsock: add initial limited implementation	Jakob Unterwurzacher
	At the moment, in forward mode you can only encrypt paths and in reverse mode you can only decrypt paths.
2016-10-19	tests: add example tar	Jakob Unterwurzacher

2016-10-19	tests: add 1980.tar.gz extract test	Jakob Unterwurzacher
	Test that we get the right timestamp when extracting a tarball. Also simplify the workaround in doTestUtimesNano() and fix the fact that it was running no test at all.
2016-10-16	tests: split "normal" tests into "cli" and "defaults"	Jakob Unterwurzacher
	Also fixes the failure to run the benchmarks do to the missing gocryptfs.diriv.