| Age | Commit message (Collapse) | Author | 
 | 
This is how this should be done as well in future test scripts.
 | 
 | 
 | 
 | 
This currently fails as reported in
https://github.com/rfjakob/gocryptfs/issues/35 .
Also remove the spurious sleep in the test.
 | 
 | 
Make sure setting nanoseconds works by path and fd.
 | 
 | 
This obsoletes loopback-mem.bash.
 | 
 | 
"canonical-benchmarks.bash TESTDIR"
can now be used on any filesystem.
 | 
 | 
Simple script that finds out the maximum supported filename
length.
 | 
 | 
Helps to find memory leaks in go-fuse's loopback, which
gocryptfs builds upon.
 | 
 | 
loopback is an example app that comes with the go-fuse lib.
It uses all the same APIs as gocryptfs, minus the encryption.
 | 
 | 
Pass "-encfs" to test encfs instead of gocryptfs.
 | 
 | 
 | 
 | 
 | 
 | 
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
 | 
 | 
"go tool vet -shadow=true" complained about the md5 package
being shadowed by variables called "md5".
Fix by using the Md5hex helper and dropping the md5 import.
 | 
 | 
On Linux, Blksize is already int64. But on OSX
it is int32 and that caused a compile failure.
https://github.com/rfjakob/gocryptfs/issues/15
 | 
 | 
...and convert all calls to syscall.{Fallocate,Openat}
to syscallcompat .
Both syscalls are not available on OSX. We emulate Openat and just
return EOPNOTSUPP for Fallocate.
 | 
 | 
Reported at https://github.com/rfjakob/gocryptfs/issues/15
 | 
 | 
Mode=0 (default) and mode=1 (keep size) are supported.
The patch includes test cases and the whole thing passed xfstests.
Fixes https://github.com/rfjakob/gocryptfs/issues/1 .
 | 
 | 
We were growing the file block-by-block which was pretty
inefficient. We now coalesce all the grows into a single
Ftruncate. Also simplifies the code!
Simplistic benchmark: Before:
  $ time truncate -s 1000M foo
  real	0m0.568s
After:
  $ time truncate -s 1000M foo
  real	0m0.205s
 | 
 | 
...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.
 | 
 | 
...and add tests for checking that gocryptfs.diriv
does not get created.
The main "integration_tests" package has become quite
big and convoluted over time.
This small separate package should make writing tests
for "-plaintextnames" easier.
As seen in "fusefrontend: fix PlaintextNames versions of Mkdir, Rmdir",
we need more of them.
 | 
 | 
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.
 | 
 | 
From the man page:
  **-ro**
  :      Mount the filesystem read-only
Also add a test.
 | 
 | 
 | 
 | 
* Supports stdin
* Add tests for extpass and stdin
As per user request at https://github.com/rfjakob/gocryptfs/issues/30
 | 
 | 
Also, capture all stderr and stdout but pass "-q".
This way we get to see error messages if there are any, or
spurious output when there should be none due to "-q".
 | 
 | 
Mounts two gocryptfs filesystems, "ping" and "pong" and moves the
linux-3.0 kernel tree back and forth between them.
When called as "pingpong-rsync.bash" it uses "rsync --remove-source-files"
for moving the files, otherwise plain "mv".
 | 
 | 
We (actually, go-fuse) used to call Chown() instead of Lchown()
which meant that the operation would fail on dangling symlinks.
Fix this by calling os.Lchown() ourself. Also add a test case
for this.
 | 
 | 
This file will also be used by other tests, so it should
have a generic name.
 | 
 | 
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.
 |