libgocryptfs/tests
Sebastian Lackner 9f56b33e0c fusefrontend: Fix longname handling for renames with existing target
Fixes https://github.com/rfjakob/gocryptfs/issues/170

Steps to reproduce the problem:

* Create a regular forward mount point
* Create a file with a shortname and one with a long filename
* Try to run 'mv <shortname> <longname>'

This should actually work and replace the existing file, but instead it
fails with:

    mv: cannot move '<shortname>' to '<longname>': File exists

The problem is the creation of the .name file. If the target already exists
we can safely ignore the EEXIST error and just keep the existing .name file.
2017-11-25 16:19:09 +01:00
..
cli main: Add '-devrandom' commandline option 2017-11-21 23:37:06 +01:00
defaults tests: add diriv cache race test 2017-08-10 21:01:19 +02:00
example_filesystems tests: Add test for access to encrypted version of '.' and '..' 2017-11-23 08:48:00 +01:00
hkdf_sanity tests: add hkdf_sanity tests with broken example filesystem 2017-03-18 16:48:58 +01:00
matrix fusefrontend: Fix longname handling for renames with existing target 2017-11-25 16:19:09 +01:00
plaintextnames Fix misspellings 2016-10-24 19:18:13 +02:00
reverse fusefrontend_reverse: workaround ext4 test failure 2017-10-03 21:15:17 +02:00
stress_tests tests: fsstress-gocryptfs.bash: sync up with EncFS 2017-07-21 23:34:44 +02:00
test_helpers fusefrontend: implement path decryption via ctlsock 2017-05-07 21:01:39 +02:00
canonical-benchmarks.bash benchmarks: add streaming read benchmark 2017-06-27 00:04:58 +02:00
dl-linux-tarball.bash tests: OSX compat: use OSX-style "stat -f" 2017-02-16 19:10:36 +01:00
fuse-unmount.bash OSX compat: replace fusermount calls with fuse-unmount.bash 2017-02-15 23:02:01 +01:00
maxlen.bash maxlen.bash: result was 1 too high 2016-10-04 10:26:22 +02:00