gocryptfs, branch v1.7.1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7.1 2019-10-06T20:35:27+00:00 Update README for v1.7.1 2019-10-06T20:35:27+00:00 Jakob Unterwurzacher 2019-10-06T20:35:27+00:00 urn:sha1:8cb104f004cc5d3343bc3b5ef2187c1830e00f19 stress_tests: use /var/tmp by default 2019-10-06T20:34:19+00:00 Jakob Unterwurzacher 2019-10-06T20:34:19+00:00 urn:sha1:65bc006a78c67b8f8cf0b01f8ed948dca6c1e408 There is a good chance that /tmp is tmpfs, and we want to run our tests on a real filesystem. test.bash: export TMPDIR 2019-10-06T19:56:01+00:00 Jakob Unterwurzacher 2019-10-06T19:56:01+00:00 urn:sha1:a1f647740182a74eb84eed3135b0f171ac753fdb We have to export TMPDIR, otherwise the Go tests to not pick it up. travis: also test Go 1.12.x 2019-10-06T19:53:50+00:00 Jakob Unterwurzacher 2019-10-06T19:53:50+00:00 urn:sha1:f9f3c6ac5c872a5d50f332f19defd3711bd5c1b1 tests: use /var/tmp by default 2019-10-06T19:53:20+00:00 Jakob Unterwurzacher 2019-10-06T19:50:27+00:00 urn:sha1:8c4429408716d9890a98a48c246d616dbfea7e31 On Fedora, /tmp is tmpfs, which behaves differently than ext4 (inode numbers are never reused, for example). Use /var/tmp, which is ext4 on Fedora, to get a more realistic test environment. This also allows us to drop the xattr workaround. fusefrontend: unregister from openfiletable before closing the fd 2019-10-06T19:47:36+00:00 Jakob Unterwurzacher 2019-10-06T19:27:38+00:00 urn:sha1:00af4f48643f0533b6cfbd14fdf5186c844f8f5d Closing the fd means the inode number may be reused immediately by a new file, so we have to get the old fileID out of the table beforehand! Hopefully fixes https://github.com/rfjakob/gocryptfs/issues/363 fusefrontend: print file hexdump on header error 2019-10-06T17:37:51+00:00 Jakob Unterwurzacher 2019-10-06T17:36:04+00:00 urn:sha1:43265940fa2d43ebea8edb00373aa4d6718e2ea7 This should help debugging https://github.com/rfjakob/gocryptfs/issues/363 , but does no harm in normal operation as it only prints ciphertext to the log. contentenc: add explicit test for all-zero header 2019-10-06T17:37:51+00:00 Jakob Unterwurzacher 2019-10-06T17:34:32+00:00 urn:sha1:b3c88f573f4c1b269e78dd7d1dbd6de73d477694 https://github.com/rfjakob/gocryptfs/issues/363 tests: filter leaked fds by prefix 2019-10-06T17:37:51+00:00 Jakob Unterwurzacher 2019-10-06T17:04:16+00:00 urn:sha1:1fb18f4a9ef2bbbc6e7c774fa064808a3952bb3f When running $ go test ./tests/matrix/ in isolation, it failed like this: fd leak? before, after: [0r=/dev/null 3w=/dev/null 5r=/proc/8078/fd (hidden:4)] [0r=/dev/null 3w=/dev/null 5w=/tmp/go-build366655199/b001/testlog.txt 7r=/proc/8078/fd (hidden:4)] Filter by prefix to get rid of this spurious test failure. tests: clarify which process seems to be leaking fds 2019-10-06T16:48:09+00:00 Jakob Unterwurzacher 2019-10-06T16:48:09+00:00 urn:sha1:d361f6e35bb97ef8f060131ea5b29f922e613c49 The tests check if they leak fds themselves, but we also check if gocryptfs leaks fds. Clarify what is what in the error message.