libgocryptfs/internal/fusefrontend_reverse
Jakob Unterwurzacher 719693ec5d fusefrontend[_reverse]: move crypto init up to caller
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).
2018-02-18 11:21:58 +01:00
..
ctlsock_interface.go gccgo: replace syscall.NAME_MAX with unix.NAME_MAX 2018-02-01 23:50:11 +01:00
reverse_longnames.go gccgo: replace syscall.NAME_MAX with unix.NAME_MAX 2018-02-01 23:50:11 +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]: move crypto init up to caller 2018-02-18 11:21:58 +01:00
rpath_cache.go fusefrontend_reverse: use OpenNofollow in findLongnameParent 2018-01-17 20:54:05 +01:00
rpath.go fusefrontend_reverse: use OpenNofollow in findLongnameParent 2018-01-17 20:54:05 +01:00
virtualfile.go fusefrontend_reverse: use OpenNofollow in virtualFile.GetAttr 2018-01-17 21:36:38 +01:00