| Age | Commit message (Collapse) | Author | 
 | 
 | 
 | 
The old implementation of counting up from a random starting
point had the problem that is allowed an attacker to find out
the write order of the blocks.
 | 
 | 
 | 
 | 
main_test_tmp -> tmp
	main_benchmark.bash -> benchmark.bash
 | 
 | 
Futimes() only takes microsecond resolution while the FUSE call
Utimens() wants nanosecond precision.
This is why UTIME_OMIT did not work - this change fixes the
xfstests generic/258 test failure.
The go library does not provide a FutimesNano() function which is
why I use UtimesNano() on /proc/self/fd/n.
This is what the Go library does in Futimes().
 | 
 | 
The implementation was incomplete, disable fallocate completely for now.
See https://github.com/rfjakob/gocryptfs/issues/1
Fixes xfstests generic/075
 | 
 | 
The bug was caused by using cipherOff where plainOff should
have been used.
Renamed the symbols for less confusion.
 | 
 | 
 | 
 | 
Uncovered by running xfstests generic/014 several times
 | 
 | 
Fixes xfstests generic/002
 | 
 | 
 | 
 | 
Development has focused on PathFS for some time now and things are
working well.
 | 
 | 
"Offset" is unclear whether it is an offset from the start of file
or start of block. "Skip" seems much better.
 | 
 | 
Cuts down the runtime of xfstests generic/014
from 1822 seconds to 36 seconds
 | 
 | 
Fixes TestFileHoles test
 | 
 | 
Also, fix key, it is now []byte, not [16]byte
 | 
 | 
Create a file with holes by writing to offset 0 (block #0) and
offset 4096 (block #1).
This test currently fails.
 | 
 | 
The actual fix is
	oldSize := f.cfs.PlainSize(uint64(fi.Size()))
the rest is logging improvements
 | 
 | 
 | 
 | 
Makes the log output smaller and more readable.
 | 
 | 
Fixes xfstests generic/010
Note that file holes are not authenticated,
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Filesystem is set to CIPHERDIR, Type is set to fuse.gocryptfs
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Immediate speedup from 70MB/s to 80MB/s on streaming write.
Enables later parallelization.
 | 
 | 
 | 
 | 
This fixes relative symlinks:
$ tar xf linux-4.2.tar.gz
tar: linux-4.2/tools/testing/selftests/powerpc/vphn/vphn.h: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/vphn/vphn.c: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/stringloops/memcmp_64.S: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/primitives/word-at-a-time.h: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/primitives/asm/asm-compat.h: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/copyloops/memcpy_power7.S: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/copyloops/memcpy_64.S: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/copyloops/copyuser_power7.S: Cannot utime: No such file or directory
tar: linux-4.2/tools/testing/selftests/powerpc/copyloops/copyuser_64.S: Cannot utime: No such file or directory
tar: linux-4.2/arch/powerpc/boot/dts/include/dt-bindings: Cannot utime: No such file or directory
tar: linux-4.2/arch/mips/boot/dts/include/dt-bindings: Cannot utime: No such file or directory
tar: linux-4.2/arch/metag/boot/dts/include/dt-bindings: Cannot utime: No such file or directory
tar: linux-4.2/arch/arm64/boot/dts/include/dt-bindings: Cannot utime: No such file or directory
tar: linux-4.2/arch/arm/boot/dts/include/dt-bindings: Cannot utime: No such file or directory
tar: Exiting with failure status due to previous errors
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
The too-large reported value broke mmap
(applications saw appended zero bytes)
Also
* Add locking for all fd operations
* Add "--debug" command line switch
 | 
 | 
Also, re-enable openssl and disable debug messages so testing
gocryptfs is less painful
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Fix issues in read and write paths.
Now passes selftest.
 | 
 | 
Currently fails main_test.go, will be fixed in part II
 |