Closed a-xin closed 10 years ago
:+1: storing your keyfile outside of your cloud storage folder is recommended by the encfs author. Being able to select it from a local path on my device would be nice.
Agreed, this would be good. I'm trying to think of how to do this in a user friendly way with the current UI - any ideas? Maybe in the "Import Volume" mode if we don't detect an .encfs6.xml when the user clicks the import icon, we can ask if they would like to import with a local keyfile? What about the volume create workflow?
Yeah, having it as a fallback seems nice - doesn't burden users who have the keyfile stored in their volume, but gives power users a choice. New volume creation could just always drop the keyfile in the volume as it does now - power users can move it aside safely if they want to. People as paranoid as me are probably going to be setting up volumes outside of the app/managing the keyfile carefully anyway :)
+1 Any progress on this?
No progress yet. Patches welcome :) I'll hopefully get around to this sometime (it's in the top 3 most pressing issues).
This is done thanks to the efforts of ashjas. Will be released as 2.1 within a few weeks.
Please add support for external config files. I tried to open a volume that was created using encfs --reverse, so the config file is not in the folder of the encrypted data and there fore encdroid does not seem to find it...