gocryptfs/tests/example_filesystems, branch v1.7-rc2Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7-rc22018-12-27T14:19:55+00:00Assorted spelling fixes.2018-12-27T14:19:55+00:00Sebastian Lackner2018-12-27T11:03:00+00:00urn:sha1:874eaf9734cc10940e08f7b043652449e1e220b5
Mostly detected with the 'codespell' utility, but also includes some
manual grammar fixes.
tests: example_filesystems: create a private copy in /tmp2018-05-04T20:27:59+00:00Jakob Unterwurzacher2018-05-04T20:27:59+00:00urn: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` functionality2018-03-21T23:02:10+00:00Jakob Unterwurzacher2018-03-21T23:02:10+00:00urn: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:00Sebastian Lackner2017-11-23T00:38:30+00:00urn:sha1:d257bb34c1dd478cdb62c0d19c3e280d4f8649b4
To show that https://github.com/rfjakob/gocryptfs/issues/163 has been fixed.
fusefrontend_reverse: fix 176-byte names2017-10-01T11:50:25+00:00Jakob Unterwurzacher2017-10-01T11:50:25+00:00urn: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 filesystem2017-05-30T15:04:46+00:00Jakob Unterwurzacher2017-05-28T17:02:22+00:00urn: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 default2017-03-07T19:56:50+00:00Jakob Unterwurzacher2017-03-06T21:59:30+00:00urn:sha1:efc88346bec52675d5243f988aa3386d617ee1c4
This brings the CLI options back in sync with the default
feature flags.
tests: recreate v1.3 example filesystem2017-03-07T19:56:50+00:00Jakob Unterwurzacher2017-03-06T21:53:49+00:00urn:sha1:f1244b6d06a4932e8a51adedf351ec83262c2db5
The filesystem was created with a gocryptfs version that ignored
the HKDF flag (hence everything was actually encrypted WITHOUT hkdf).
Fix it by recreating it.
cli: add "-hkdf" option2017-03-07T19:56:50+00:00Jakob Unterwurzacher2017-03-06T21:43:55+00:00urn:sha1:2362e67a9e5c6f1c96e987e8753eca295f283875
This commit also enables actually passing the HKDF setting to
fusefrontend, this was missing till now.
tests: add v1.3 example filesystem2017-03-05T22:07:52+00:00Jakob Unterwurzacher2017-03-05T22:06:40+00:00urn:sha1:b7538fc026dc25d0061e08bedc4b3aff97bb52d2
This filesystem has both HKDF and Raw64 enabled.