| Age | Commit message (Collapse) | Author | 
 | 
This brings the CLI options back in sync with the default
feature flags.
 | 
 | 
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.
 | 
 | 
This commit also enables actually passing the HKDF setting to
fusefrontend, this was missing till now.
 | 
 | 
This filesystem has both HKDF and Raw64 enabled.
 | 
 | 
Yields a nice reduction in code size.
 | 
 | 
Calling t.Fatal immeadiately aborts the test, which means the
filesystem will not get unmounted, which means test.bash will
hang.
 | 
 | 
You will still get lots of test error, but at least the tests
will run.
 | 
 | 
Calling t.Fatal means that the parent test has no chance
to clean up.
 | 
 | 
Fix the test for that and add checks in example_filesystems_test.
 | 
 | 
 | 
 | 
 | 
 | 
Also move the example content into "content".
 | 
 | 
As reverse also does not want a diriv file, the "plaintextNames"
argument became a misnomer.
 | 
 | 
Go versions 1.4 and lower lack NewGCMWithNonceSize(), which causes
a panic in the test.
 | 
 | 
 | 
 | 
This should make it work on OSX.
Also, split unmount into two functions. Depending on what you
want,
* UnmountErr returns the resulting error
* UnmountPanic panics if the error was not nil
 | 
 | 
...into "matrix" and "normal".
Also:
* Make running multiple packages in parallel safe, see
  http://stackoverflow.com/questions/23715302/go-how-to-run-tests-for-multiple-packages
* Don't depent on test_helper.TmpDir and friends to have a terminating slash
 | 
 | 
Run the tests twice, once with openssl and once with Go crypto.
 | 
 | 
This file was forgotten in commit
"tests: make tests for unsupported FSs more compact".
 | 
 | 
The GCMIV128 feature flag is already mandatory, dropping the command
line option is the final step.
Completes https://github.com/rfjakob/gocryptfs/issues/29 .
 | 
 | 
There is no need to test that deprecated command-line options
produce an error. I trust the flags package.
Also split the example_filesystem helper functions into a
separate file.
 | 
 | 
The EMENames feature flag is already mandatory, dropping the command
line option is the final step.
 | 
 | 
The DirIV feature flag is already mandatory, dropping the command
line option is the final step.
 | 
 | 
The v0.6-plaintextnames example FS lacks the GCMIV128 feature
flag, is no longer mountable and can no longer be used for testing.
Add a new "-plaintextnames" filesystem created by gocryptfs v0.7.
There have been no format changes to "-plaintextnames" since then.
 | 
 | 
 | 
 | 
The v0.6 and older example filesystem are mounted read-only
because they are deprecated, so skip the read-write tests.
 | 
 | 
extpass_test and example_filesystems_test did it wrong,
always returning 0.
 | 
 | 
Running these tests from integration_tests' TestMain() was awkward
because they were run twice with unchanged settings.
integration_tests tests everything with OpenSSL and with native
Go crypto, but this does not take affect for the example filesystems.
To make this work, test_helpers is also split into its own package.
 |