gocryptfs/tests/example_filesystems, branch v2.0.1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0.1 2021-06-02T12:29:48+00:00 nametransform: check name validity on encryption 2021-06-02T12:29:48+00:00 Jakob Unterwurzacher 2021-06-02T12:21:30+00:00 urn:sha1:04858ddd222bbf7156f33f99cfb293a9b1e15ec8 xfstests generic/523 discovered that we allowed to set xattrs with "/" in the name, but did not allow to read them later. With this change we do not allow to set them in the first place. test_helper: VerifyExistence: don't panic 2020-08-15T13:39:08+00:00 Jakob Unterwurzacher 2020-08-15T13:39:08+00:00 urn:sha1:f270135c1614843f43a9df0e68b6e3fa556b6774 Instead bubble up the error to the testing object. Fix "go get" failure 2019-12-23T23:38:40+00:00 Jakob Unterwurzacher 2019-12-23T23:38:40+00:00 urn:sha1:7dda2363e1f8d30d5ebce5b6279452a2cf1bb77a Move the statusTxtContent to fix this confusing error when running `go get github.com/rfjakob/gocryptfs/...`: $ go get github.com/rfjakob/gocryptfs/... # github.com/rfjakob/gocryptfs/tests/example_filesystems tests/example_filesystems/example_test_helpers.go:22:16: undefined: statusTxtContent tests/example_filesystems/example_test_helpers.go:75:16: undefined: statusTxtContent Assorted spelling fixes. 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. tests: example_filesystems: create a private copy in /tmp 2018-05-04T20:27:59+00:00 Jakob Unterwurzacher 2018-05-04T20:27:59+00:00 urn:sha1:fc8fca04a8139de3683afb9c7c354dbbb151e490 The tests write to the example_filesystems folder, which 1) May leave your source tree in a modified state 2) Triggers test failures when the fsck tests run concurrently, which happens on Travis CI every now and then. Fix both problem by copying the example_filesystems folder to a private location in /tmp. Add `-masterkey=stdin` functionality 2018-03-21T23:02:10+00:00 Jakob Unterwurzacher 2018-03-21T23:02:10+00:00 urn:sha1:9bc039a4bac6b51d9ebe116de5c311e90343a088 https://github.com/rfjakob/gocryptfs/issues/218 tests: Add test for access to encrypted version of '.' and '..' 2017-11-23T07:48:00+00:00 Sebastian Lackner 2017-11-23T00:38:30+00:00 urn:sha1:d257bb34c1dd478cdb62c0d19c3e280d4f8649b4 To show that https://github.com/rfjakob/gocryptfs/issues/163 has been fixed. 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 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. cli: enable "-raw64" by default 2017-03-07T19:56:50+00:00 Jakob Unterwurzacher 2017-03-06T21:59:30+00:00 urn:sha1:efc88346bec52675d5243f988aa3386d617ee1c4 This brings the CLI options back in sync with the default feature flags.