gocryptfs/internal/nametransform, branch v1.6

fusefrontend: doWrite: delete file header if first write fails

2018-07-15T13:12:55+00:00

xfstests generic/083 fills the filesystem almost completely while running fsstress in parallel. In fsck, these would show up: readFileID 2580: incomplete file, got 18 instead of 19 bytes This could happen when writing the file header works, but writing the actual data fails. Now we kill the header again by truncating the file to zero.

WriteDirIV: delete incomplete gocryptfs.diriv file if write fails

2018-07-15T10:02:39+00:00

If the underlying filesystem is full, writing to gocryptfs.diriv may fail, and later fsck show this: OpenDir "xyz": could not read gocryptfs.diriv: wanted 16 bytes, got 0 Uncovered by xfstests generic/083. Also fixes a fd leak in the error path.

fsck: clean up log output

2018-04-02T16:32:30+00:00

Make sure we get only 1 warning output per problem. Also, add new corruption types to broken_fs_v1.4.

gccgo: replace syscall.NAME_MAX with unix.NAME_MAX

2018-02-01T22:50:11+00:00

For some reason the syscall.NAME_MAX constant does not exist on gccgo, and it does not hurt us to use unix.NAME_MAX instead. https://github.com/rfjakob/gocryptfs/issues/201

fusefrontend: Improve documentation of mkdirWithIv and WriteDirIV

2017-12-01T08:41:52+00:00

As requested in https://github.com/rfjakob/gocryptfs/pull/179

syscallcompat: check that we get NOFOLLOW wherever possible

2017-11-30T18:40:53+00:00

...and fix the instances where the AT_SYMLINK_NOFOLLOW / O_NOFOLLOW / O_EXCL flag was missing.

fusefrontend: allow_other: close race between mkdir and chown

2017-11-29T12:28:04+00:00

Fixes the same problem as described in 72b975867a3b9bdf53fc2da62e2ba4a328d7e4ab, except for directories instead of device nodes.

syscallcompat: Introduce unlinkat syscall with flags argument

2017-11-29T11:41:23+00:00

fusefrontend: Fix longname handling for renames with existing target

2017-11-25T15:19:09+00:00

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 ' This should actually work and replace the existing file, but instead it fails with: mv: cannot move '' to '': 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.

nametransform: Return error if decrypted name is '.' or '..'

2017-11-22T22:42:08+00:00