gocryptfs/internal/fusefrontend_reverse, branch v1.4.3

fusefrontend_reverse: use OpenNofollow in virtualFile.GetAttr

2018-01-17T20:36:38+00:00

Makes it robust against symlink races. Final piece, closes https://github.com/rfjakob/gocryptfs/issues/165

fusefrontend_reverse: use OpenNofollow in findLongnameParent

2018-01-17T19:54:05+00:00

Protects findLongnameParent against symlink races. Also add comments to several functions along the way. Reported at https://github.com/rfjakob/gocryptfs/issues/165

Run go fmt

2018-01-16T22:18:53+00:00

fusefrontend_reverse: Use O_DIRECTORY in OpenDir implementation

2017-12-11T20:18:20+00:00

Also get rid of the defer - it is not really necessary here.

fusefrontend_reverse: Reject access to device nodes in newFile function

2017-12-11T08:55:16+00:00

Steps to reproduce: * Create a regular reverse mount point * Create a file "test" in the original directory * Access the corresponding encrypted directory in the mount point (ls ) * Quickly delete the file in the original data - instead create a device node * Access the file again, it will access the device node and attempt to read from it Fixes https://github.com/rfjakob/gocryptfs/issues/187

fusefrontend_reverse: Use openBackingDir in GetAttr

2017-12-07T22:36:11+00:00

Also fixes 48bd59f38843e5ebd4e4c9f666f1aea1c9990803 - the directory FD should also be closed in case of an error.

fusefrontend_reverse: Use openBackingDir in Readlink

2017-12-07T22:36:11+00:00

fusefrontend_reverse: fix fd leak in GetAttr

2017-12-07T08:01:12+00:00

Fixes https://github.com/rfjakob/gocryptfs/issues/184

fusefrontend_reverse: secure Access against symlink races (somewhat)

2017-12-06T23:11:35+00:00

Unfortunately, faccessat in Linux ignores AT_SYMLINK_NOFOLLOW, so this is not completely atomic. Given that the information you get from access is not very interesting, it seems good enough. https://github.com/rfjakob/gocryptfs/issues/165

fusefrontend_reverse: secure Readlink against symlink races

2017-12-06T20:13:08+00:00

...by using Readlinkat. Tracking ticket: https://github.com/rfjakob/gocryptfs/issues/165