| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | Fix the test for that and add checks in example_filesystems_test. | 
|  |  | 
|  |  | 
|  | Also move the example content into "content". | 
|  | Only in plaintextnames-mode AND with the config file at the
default location it will be mapped into the mountpoint.
Also adds a test for that. | 
|  | We want to see panics and warnings on the console | 
|  | As reverse also does not want a diriv file, the "plaintextNames"
argument became a misnomer. | 
|  | Future tests will need more info about the running test case. | 
|  | And add AES-SIV | 
|  |  | 
|  |  | 
|  | Go versions 1.4 and lower lack NewGCMWithNonceSize(), which causes
a panic in the test. | 
|  | This file does not exist on all systems, causing spurious
test failures.
See #40, #43 | 
|  | The expected allocated sizes are verified for tmpfs and ext4.
btrfs gives different results, but that's not an error.
Also, simplify test_helpers.Du and several code paths.
Fixes #43. | 
|  | Additionally, output 0 instead of 7 on permission errors. | 
|  | GCM-SIV is not yet finalized, and the reference implemenation is
painfully slow at about 2 MB/s. Switch to AES-SIV. | 
|  |  | 
|  | Also delete the unused "dirIVNameStruct", found by deadcode. | 
|  |  | 
|  | Now also verifies the returned file size. | 
|  |  | 
|  | Look at the error code from os.Remove and decide about the
right thing to do.
Gets rid of spurious fusermount error messages. | 
|  |  | 
|  | 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. |