gocryptfs/internal/fusefrontend_reverse, branch v1.6.1

fusefrontend_reverse: reject excludes for the root directory ""

2018-08-15T10:28:29+00:00

This is most likely a mistake by the user. Reject it.

reverse mode: add --exclude option

2018-08-11T21:26:49+00:00

https://github.com/rfjakob/gocryptfs/issues/235

darwin does not have PATH_MAX

2018-06-07T22:47:48+00:00

Define our own, with the value from Linux.

fusefrontend[_reverse]: move crypto init up to caller

2018-02-18T10:21:58+00:00

Both fusefrontend and fusefrontend_reverse were doing essentially the same thing, move it into main's initFuseFrontend. A side-effect is that we have a reference to cryptocore in main, which will help with wiping the keys on exit (https://github.com/rfjakob/gocryptfs/issues/211).

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_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