| Age | Commit message (Collapse) | Author | 
 | 
Also drop Go 1.4 from Travis CI and update other Go
versions to latest point release.
 | 
 | 
There are two independent backends, one for name encryption,
the other one, AEAD, for file content.
"BackendTypeEnum" only applies to AEAD (file content), so make that
clear in the name.
 | 
 | 
Version 1.1 of the EME package (github.com/rfjakob/eme) added
a more convenient interface. Use it.
Note that you have to upgrade your EME package (go get -u)!
 | 
 | 
Calling t.Fatal immeadiately aborts the test, which means the
filesystem will not get unmounted, which means test.bash will
hang.
 | 
 | 
Sourcing the script breaks the "cd $(dirname $0)" logic in
build-without-openssl.bash.
 | 
 | 
 | 
 | 
When filename encryption is active, every directory contains
a "gocryptfs.diriv" file. This file should also change the owner.
Fixes https://github.com/rfjakob/gocryptfs/issues/86
 | 
 | 
We have it saved in Stderr and Stdout anyway, let's free this fd
number.
 | 
 | 
The old ones were rendered by github almost as big as the parent headings.
 | 
 | 
Correcting year in changelog (1.2.1)
 | 
 | 
 | 
 | 
You will still get lots of test error, but at least the tests
will run.
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
This really only handles scrypt and no other key-derivation functions.
Renaming the files prevents confusion once we introduce HKDF.
renamed:    internal/configfile/kdf.go -> internal/configfile/scrypt.go
renamed:    internal/configfile/kdf_test.go -> internal/configfile/scrypt_test.go
 | 
 | 
This makes it easier to use the package in external projects.
See https://github.com/rfjakob/gocryptfs/issues/79
 | 
 | 
 | 
 | 
 | 
 | 
Old Go versions miss cipher.NewGCMWithNonceSize, which causes:
  internal/speed/speed.go:95: undefined: cipher.NewGCMWithNonceSize
 | 
 | 
A crypto benchmark mode like "openssl speed".
Example run:
  $ ./gocryptfs -speed
  AES-GCM-256-OpenSSL 	 180.89 MB/s	(selected in auto mode)
  AES-GCM-256-Go      	  48.19 MB/s
  AES-SIV-512-Go      	  37.40 MB/s
 | 
 | 
In Go 1.8, os.Rename refuses to overwrite an empty directory.
Switch to syscall.Rename, which still does the right thing.
 | 
 | 
(Currently failing the tests!)
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Mac OS X flock does not support "--nonblock", but does support "-n":
https://github.com/discoteq/flock/blob/master/man/flock.1.ronn
Skip the openssl build because it requires
1) openssl
2) fixing the import paths in gocryptfs
Reported at https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-280464400
 | 
 | 
Otherwise the build fails once you have more than 50 commits
since the last tag.
You'd get:
$ ./build.bash
fatal: No names found, cannot describe anything.
 | 
 | 
 | 
 | 
These were currently passed to decryptPath() were it caused
a warning.
 | 
 | 
 | 
 | 
Linux has st.Atim, st.Mtim,
OSX hat st.Atimespec, st.Mtimespec.
Reported at https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-279130217
 | 
 | 
As suggested by
https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-279130217
 | 
 | 
Mac OS X does not have /proc.
Reported at https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-279130217
 | 
 | 
Reported at https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-279130217
 | 
 | 
On OSX, /usr/bin/time does not support "-f".
Reported in https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-279130217 .
 | 
 | 
Does not exist on OSX
Reported in https://github.com/rfjakob/gocryptfs/issues/15
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
...instead of having separate compatability logic.
 | 
 | 
Mac OS X does not have fusermount and uses umount instead.
The fuse-unmount.bash calls the appropriate command.
 | 
 | 
 | 
 | 
This used to hang at 100% CPU:
    cat /dev/zero | gocryptfs -init a
...and would ultimately send the box into out-of-memory.
The number 1000 is chosen arbitrarily and seems big enough
given that the password must be one line.
Suggested by @mhogomchungu in https://github.com/rfjakob/gocryptfs/issues/77 .
 | 
 | 
Closes https://github.com/rfjakob/gocryptfs/issues/77
 | 
 | 
From the comment:
// CheckTrailingGarbage tries to read one byte from stdin and exits with a
// fatal error if the read returns any data.
// This is meant to be called after reading the password, when there is no more
// data expected. This helps to catch problems with third-party tools that
// interface with gocryptfs.
 | 
 | 
 | 
 | 
 | 
 | 
If the user has already saved the master key and is not
aware of "-q" the master key needlessly ends up in the terminal
buffer.
Closes https://github.com/rfjakob/gocryptfs/issues/76
 |