Feature: Allow shadowing cipherdir with mountpoint

[Atrate]

It would be nice if gocryptfs allowed shadowing the cipherdir with its decrypted mountpoint, like ecryptfs.

I am not knowledgeable enough as to whether FUSE supports it or whether it's possible to do without superuser rights/a kernel module, so I'm just throwing the idea here.

Current behavior:

> gocryptfs /tmp/tmp.2CrICJxW7V/test /tmp/tmp.2CrICJxW7V/test
Mountpoint "/tmp/tmp.2CrICJxW7V/test" would shadow cipherdir "/tmp/tmp.2CrICJxW7V/test", this is not supported

[rfjakob]

Hi, this is theoretically possible, but isn't it just super confusing?

[Atrate]

I guess I just got used to the way ecryptfs allows it and it became convenient for me to not have to keep track of two separate directories.

[kaoneko]

On the contrary, it makes a lot of sense (from an end-user perspective) to point gocryptfs at a directory in order decrypt it, or unlock it, without having to look in another place to view the decrypted content.

I wrote a wrapper script that just takes CIPHERDIR as an argument, renames it to .CIPHERDIR (hidden folder) and then mounts it on CIPHERDIR after recreating the folder. And does the reverse when CIPHERDIR is already a fuse.gocryptfs mountpoint. The resulting experience feels very natural.

Just like some apps or operating systems offer a "locked folder" for your most sensitive files, that you gain access to only after authenticating upon opening it; the "unlocking the vault" experience.