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
..
args.go	main: purge masterkey from memory as soon as possible	2017-08-11 19:02:26 +02:00
ctlsock_interface.go	fusefrontend: implement path decryption via ctlsock	2017-05-07 21:01:39 +02:00
file_allocate_truncate.go	fusefrontend: Read: use provided buffer	2017-06-30 23:11:38 +02:00
file_holes.go	fusefrontend: truncateGrowFile: avoid createHeader() call	2017-03-12 21:06:59 +01:00
file.go	Revert most of "fusefrontend: clamp oversized reads"	2017-10-21 17:43:21 +02:00
fs_dir.go	macos: automatically remove .DS_Store on Rmdir	2017-09-05 22:47:15 +02:00
fs.go	fusefrontend: Fix longname handling for renames with existing target	2017-11-25 16:19:09 +01:00
names.go	nametransform: delete unused function DecryptPathDirIV	2016-09-25 18:56:23 +02:00