gocryptfs/tests, branch v1.4.2 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4.2 2017-10-03T19:15:17+00:00 fusefrontend_reverse: workaround ext4 test failure 2017-10-03T19:15:17+00:00 Jakob Unterwurzacher 2017-10-03T19:15:17+00:00 urn:sha1:64e5906ffa1f225a51048b3d0ac6b1a09e2ca170 The extended TestLongnameStat() exposes a pathological case when run on ext4, as ext4 reuses inode numbers immediately. This change modifies the test to not delete the files immediately, so the inode numbers cannot be reused immediately. Fix for the underlying issue is a TODO. fusefrontend_reverse: fix 176-byte names 2017-10-01T11:50:25+00:00 Jakob Unterwurzacher 2017-10-01T11:50:25+00:00 urn:sha1:4da245c69d7994efec75e1deaef56a03020d39db A file with a name of exactly 176 bytes length caused this error: ls: cannot access ./tmp/dsg/sXSGJLTuZuW1FarwIkJs0w/b6mGjdxIRpaeanTo0rbh0A/QjMRrQZC_4WLhmHI1UOBcA/gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY: No such file or directory ls: cannot access ./tmp/dsg/sXSGJLTuZuW1FarwIkJs0w/b6mGjdxIRpaeanTo0rbh0A/QjMRrQZC_4WLhmHI1UOBcA/gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY.name: No such file or directory -????????? ? ? ? ? ? gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY -????????? ? ? ? ? ? gocryptfs.longname.QV-UipdDXeUVdl05WruoEzBNPrQCfpu6OzJL0_QnDKY.name Root cause was a wrong shortNameMax constant that failed to account for the obligatory padding byte. Fix the constant and also expand the TestLongnameStat test case to test ALL file name lengths from 1-255 bytes. Fixes https://github.com/rfjakob/gocryptfs/issues/143 . tests: add diriv cache race test 2017-08-10T19:01:19+00:00 Jakob Unterwurzacher 2017-08-10T18:55:45+00:00 urn:sha1:f59479736bed49411bda3368f419d6605f1faa78 Passes. fusefrontend_reverse: return ENOENT for undecryptable names 2017-07-27T18:31:22+00:00 Jakob Unterwurzacher 2017-07-27T18:31:22+00:00 urn:sha1:d5133ca5ac4f241ff22ef145a3605a9fdb341bb6 This was working until DecryptName switched to returning EBADMSG instead of EINVAL. Add a test to catch the regression next time. tests: check if we close stderr and stdout correctly on mount 2017-07-23T22:05:29+00:00 Jakob Unterwurzacher 2017-07-23T18:28:41+00:00 urn:sha1:318c41827cf23476b9705081f63b7f93fecba09a Currently fails, as reported at https://github.com/rfjakob/gocryptfs/issues/130 . tests: fsstress-gocryptfs.bash: sync up with EncFS 2017-07-21T21:34:44+00:00 Jakob Unterwurzacher 2017-07-21T21:31:13+00:00 urn:sha1:74e58ae8e6647a3a61e1fba302918b3eb61b576b I have added a subset of fsstress-gocryptfs.bash to EncFS as fsstress-encfs.sh, improving the code a bit. This change forward-ports these improvements to fsstress-gocryptfs.bash. fusefronted: enable writing to write-only files 2017-07-11T21:19:58+00:00 Jakob Unterwurzacher 2017-07-11T21:19:58+00:00 urn:sha1:3062de6187990f9b4f669ecd9dffdd48ee0d778f 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 benchmarks: add streaming read benchmark 2017-06-26T22:04:58+00:00 Jakob Unterwurzacher 2017-06-26T22:04:58+00:00 urn:sha1:c12a50d4c8c24ff55d682b2fed1923be4f87f182 Fix two comments 2017-06-01T16:53:57+00:00 Jakob Unterwurzacher 2017-06-01T16:53:57+00:00 urn:sha1:f44902aaaeb8f60060c2f852b66962eca1df6b99 One out-of-date and the other with a typo. tests: add v1.3-reverse example filesystem 2017-05-30T15:04:46+00:00 Jakob Unterwurzacher 2017-05-28T17:02:22+00:00 urn:sha1:e43eb36da3e72cd0f59ac978cf76a94fa87ca7cd We check the md5 sum of the encrypted version of a file to make sure we don't accidentially change the ciphertext generation.