Sebastian Lackner 96dc2ca709 fusefrontend_reverse: Reject access to device nodes in newFile function ...

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 <encrypted dir>)
* 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

2017-12-11 09:55:16 +01:00

..

ctlsock_interface.go

fusefrontend_reverse: move pathiv to its own package

2017-05-30 17:04:46 +02:00

reverse_longnames.go

fusefrontend_reverse: Do not mix up cache information for different directories

2017-11-25 16:20:48 +01:00

rfile.go

fusefrontend_reverse: Reject access to device nodes in newFile function

2017-12-11 09:55:16 +01:00

rfs.go

fusefrontend_reverse: Use openBackingDir in GetAttr

2017-12-07 23:36:11 +01:00

rpath_cache.go

fusefrontend_reverse: convert fmt.Printf calls to tlog

2017-04-01 15:49:53 +02:00

rpath.go

fusefrontend_reverse: secure Access against symlink races (somewhat)

2017-12-07 00:11:35 +01:00

virtualfile.go

nametransform: add Dir() function

2017-08-06 23:14:39 +02:00