Sebastian Lackner 90687215a4 fusefrontend_reverse: Do not mix up cache information for different directories ... Fixes https://github.com/rfjakob/gocryptfs/issues/168 Steps to reproduce the problem: * Create a regular reverse mount point * Create files with the same very long name in multiple directories - so far everything works as expected, and it will appear with a different name each time, for example, gocryptfs.longname.A in directory A and gocryptfs.longname.B in directory B * Try to access a path with A/gocryptfs.longname.B or B/gocryptfs.longname.A - this should fail, but it actually works. The problem is that the longname cache only uses the path as key and not the dir or divIV. Assume an attacker can directly interact with a reverse mount and knows the relation longname path -> unencoded path in one directory, it allows to test if the same unencoded filename appears in any other directory.		2017-11-25 16:20:48 +01:00
..
ctlsock_reverse_test_fs	Report correct symbolic link dentry sizes	2017-03-07 20:46:58 +01:00
correctness_test.go	fusefrontend_reverse: workaround ext4 test failure	2017-10-03 21:15:17 +02:00
ctlsock_test.go	fusefrontend_reverse: Do not mix up cache information for different directories	2017-11-25 16:20:48 +01:00
linux-tarball-test.bash	OSX compat: replace fusermount calls with fuse-unmount.bash	2017-02-15 23:02:01 +01:00
longname_perf_test.go	reverse: more thorough longname stat test	2016-09-25 16:43:17 +02:00
main_test.go	tests: reverse: check Access() call	2017-02-16 21:20:29 +01:00