gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2016-07-11	tests: matrix: print name in verbose output	Jakob Unterwurzacher

2016-07-11	tests: add verbose output when unmounting	Jakob Unterwurzacher

2016-07-11	tests: use unmount wrapper in ResetTmpDir	Jakob Unterwurzacher
	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
2016-07-06	tests: fix shadow warning	Jakob Unterwurzacher
	"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.
2016-07-04	tests: OSX: cast st.Blksize to int64	Jakob Unterwurzacher
	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
2016-07-03	syscallcompat: OSX: add Fallocate and Openat wrappers	Jakob Unterwurzacher
	...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.
2016-07-02	tests: call umount instead of fusermount on OSX	Jakob Unterwurzacher
	Reported at https://github.com/rfjakob/gocryptfs/issues/15
2016-07-02	fusefrontend: add fallocate support	Jakob Unterwurzacher
	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 .
2016-07-01	fusefrontend: coalesce grows in Truncate()	Jakob Unterwurzacher
	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
2016-06-30	test: split up integration_tests	Jakob Unterwurzacher
	...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
2016-06-27	tests: run example_filesystems with "-openssl=false" AND "=true"	Jakob Unterwurzacher
	Run the tests twice, once with openssl and once with Go crypto.
2016-06-27	tests: give "-plaintextnames" its own test package	Jakob Unterwurzacher
	...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.
2016-06-26	tests: add missing file "example_test_helpers.go"	Jakob Unterwurzacher
	This file was forgotten in commit "tests: make tests for unsupported FSs more compact".
2016-06-23	Drop deprecated "-gcmiv128" option	Jakob Unterwurzacher
	The GCMIV128 feature flag is already mandatory, dropping the command line option is the final step. Completes https://github.com/rfjakob/gocryptfs/issues/29 .
2016-06-23	tests: make tests for unsupported FSs more compact	Jakob Unterwurzacher
	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.
2016-06-23	Drop deprecated "-emenames" option	Jakob Unterwurzacher
	The EMENames feature flag is already mandatory, dropping the command line option is the final step.
2016-06-23	Drop deprecated "-diriv" option	Jakob Unterwurzacher
	The DirIV feature flag is already mandatory, dropping the command line option is the final step.
2016-06-23	tests: add v0.7-plaintextnames example filesystem	Jakob Unterwurzacher
	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.
2016-06-19	tests: expect mount failure for v0.6 and older example filesystems	Jakob Unterwurzacher

2016-06-16	tests: adapt for read-only operation	Jakob Unterwurzacher
	The v0.6 and older example filesystem are mounted read-only because they are deprecated, so skip the read-write tests.
2016-06-16	tests: exit with correct error code from TestMain	Jakob Unterwurzacher
	extpass_test and example_filesystems_test did it wrong, always returning 0.
2016-06-16	Add "-ro" (read-only) flag	Jakob Unterwurzacher
	From the man page: -ro : Mount the filesystem read-only Also add a test.
2016-06-16	tests: add InitFS helper	Jakob Unterwurzacher

2016-06-15	readpassword: create internal package for password reading	Jakob Unterwurzacher
	* Supports stdin * Add tests for extpass and stdin As per user request at https://github.com/rfjakob/gocryptfs/issues/30
2016-06-14	tests: spin off TestPasswd from TestInit	Jakob Unterwurzacher
	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".
2016-06-09	test: add pingpong.bash and pingping-rsync.bash	Jakob Unterwurzacher
	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".
2016-06-08	fusefrontend: fix chown on dangling symlinks	Jakob Unterwurzacher
	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.
2016-06-08	tests: rename extractloop.md5sums to linux-3.0.md5sums	Jakob Unterwurzacher
	This file will also be used by other tests, so it should have a generic name.
2016-06-07	tests: split example_filesystems into its own package	Jakob Unterwurzacher
	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.