-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: add key file support #288
Comments
(A similar idea with proposed algorithm was #78 but in a more specific context and with only one key file.) |
What you could currently do is to store the gocryptfs.conf outside the encrypted directory. When mounting, you pass the path via "-config", which is effectively like a (single) keyfile. |
Another option/workaround for current versions would be to use the keyfiles.sh (use chmod +x):
usage:
This is only a bit limited due to the fact that |
The issue has been closed, but I can't figure out how to specify a (binary) keyfile? |
Coming from e.g. TrueCrypt one might be used to using one or multiple key files to encrypt a vault. Those key files plus the password would then be needed for mounting. It would be nice to have key file support in gocryptfs.
(The
passfile
parameter currently seems too restricted in its semantics and furthermore can only be specified once.)The text was updated successfully, but these errors were encountered: