gocryptfs/tests/reverse, 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 . 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: reverse: don't run tests that ignore "-plaintextnames" twice 2017-03-07T19:53:58+00:00 Jakob Unterwurzacher 2017-03-07T19:53:58+00:00 urn:sha1:a80d798c2deab44e2abc37eeae59546f0d7eec40 TestMain() runs all tests twice, once with plaintextnames=true and once with false. Several tests mount their own filesystem and ignore the plaintextnames variable. It makes no sense to run them twice, so skip execution when plaintextnames is set. Report correct symbolic link dentry sizes 2017-03-07T19:46:58+00:00 M. Vefa Bicakci 2017-03-07T09:09:09+00:00 urn:sha1:d48ccb3ddab71773a991b8f1b062901ff5b435b0 Prior to this commit, gocryptfs's reverse mode did not report correct directory entry sizes for symbolic links, where the dentry size needs to be the same as the length of a string containing the target path. This commit corrects this issue and adds a test case to verify the correctness of the implementation. This issue was discovered during the use of a strict file copying program on a reverse-mounted gocryptfs file system. tests: reverse: check Access() call 2017-02-16T20:20:29+00:00 Jakob Unterwurzacher 2017-02-16T20:20:29+00:00 urn:sha1:62e7eb7d04793d7d629c1105a3eddf04e396ac24 OSX compat: replace fusermount calls with fuse-unmount.bash 2017-02-15T22:02:01+00:00 Jakob Unterwurzacher 2017-02-15T22:02:01+00:00 urn:sha1:ce2e610428c940c2bd5ca1790e7375117b1f6015 Mac OS X does not have fusermount and uses umount instead. The fuse-unmount.bash calls the appropriate command. ctlsock: prevent panic on invalid decrypt request 2016-11-10T22:51:47+00:00 Jakob Unterwurzacher 2016-11-10T22:51:47+00:00 urn:sha1:d8fb28a1c38cda0b013c617404ad4a768effb704 ctlsock: implement EncryptPath for reverse mode, add tests 2016-11-10T22:32:51+00:00 Jakob Unterwurzacher 2016-11-10T22:32:51+00:00 urn:sha1:c03fc46a5150715bf6aee20ce4b89d9704141220 reverse: gocryptfs.conf was missing from the directory listings 2016-10-08T20:25:08+00:00 Jakob Unterwurzacher 2016-10-08T20:25:08+00:00 urn:sha1:d25fcc6a4b095e37c77cce8f9de2ec0f12007ed5 Fix the test for that and add checks in example_filesystems_test.