chrisbuchholz / mencfs Goto Github PK

Using EncFS, when you create a new encrypted folder, it mounts it also. Also if you encrypt a folder already containing data, this will not get encrypted.

Add a encrypt action which takes a path to where the encrypted will get created. It then passes this on to EncFS, you go through the process and then it creates the folder, encrypts it and mounts it in a temporary place defined by MEncFS. When EncFS is done, MEncFS will unmount the temporary location for you, so you are ready to use the encrypted folder with MEncFS.

MEncFS should back up anything inside the folder you encrypt and when it's done, move it into the mounted volume before it unmounts it, so it gets encrypted with the folder.

Linux support will require that the whole program be structured for multi-platform usage. That means that mencfs should be smarter about the external programs it uses (bash, encfs) and that platform specific implementation of espcially GetPassword_* function in keychain.go. There should be a system to decide which to use depending on the host.

The automount capability will be platform dependent.

On Mac OS X, it should use launchd.