aboutsummaryrefslogtreecommitdiff
path: root/tests/example_filesystems/content
diff options
context:
space:
mode:
authordanim72017-03-27 22:47:45 +0200
committerJakob Unterwurzacher2017-03-28 22:58:03 +0200
commitfb1b8ced3843a449f2a85d4ee0a9d426192d82fa (patch)
tree477a3ba38dcddff4b230933c7f870df2b30e38e6 /tests/example_filesystems/content
parentdfbf642759ef33a41b1bbc874df066f170db77d6 (diff)
fusefrontend_reverse: consistent file owners for .diriv, .name files
This PR addresses the Issue #95, about "Confusing file owner for longname files in reverse mode". It affects only the reverse mode, and introduces two modifications: 1) The "gocryptfs.longname.XXXX.name" files are assigned the owner and group of the underlying plaintext file. Therefore it is consistent with the file "gocryptfs.longname.XXXX" that has the encrypted contents of the plaintext file. 2) The two virtual files mentioned above are given -r--r--r-- permissions. This is consistent with the behavior described in function Access in internal/fusefrontend_reverse/rfs.go where all virtual files are always readable. Behavior also observed in point c) in #95 . Issue #95 URL: https://github.com/rfjakob/gocryptfs/issues/95 Pull request URL: https://github.com/rfjakob/gocryptfs/pull/97
Diffstat (limited to 'tests/example_filesystems/content')
0 files changed, 0 insertions, 0 deletions