Age | Commit message (Collapse) | Author |
|
$ gocryptfs -version
gocryptfs v0.12-36-ge021b9d-dirty; go-fuse a4c968c; 2016-07-03 go1.6.2
|
|
Fixes issue #31
https://github.com/rfjakob/gocryptfs/issues/31
|
|
If it is, append "-dirty" to the hash.
|
|
As v0.4 introduced ext4-style feature flags, the on-disk format version
is unlinkely to change. Drop it from the version output to reduce
clutter. Use "gocryptfs -version -debug" to see it.
Add the Go version string because only Go 1.6 and newer have an optimized
AES-GCM implementation. This will help users to understand the performance
of their build.
|
|
This used to fail in an ugly way:
$ ./build.bash
./build.bash: line 13: go: command not found
./build.bash: line 15: [: too many arguments
./build.bash: line 20: go: command not found
|
|
"-C" is not supported on older git versions. Instead, just cd into
the directory.
See issue #20.
|
|
|
|
|
|
|
|
|
|
Example:
./gocryptfs -version
gocryptfs v0.2-20-gabcef9e-dirty; on-disk format 1
Note that you MUST compile using "./build.bash" for this to work.
|
|
This is in preparation of getting rid of the shell wrapper
|
|
...also adapt the cryptfs tests for 256 bit long keys
|