-
Notifications
You must be signed in to change notification settings - Fork 59
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
How to mount volume created in SiriKali from command line? #17
Comments
No,these backends are not aware of the implementation of "key+keyfile" option as SiriKali generates a passphrase that is a combination of a key and a keyfile and passes on the result as a passphrase to these backends. The passphrase is generated with the below formular: You can use a CLI tool "hmac256"[1](DO NOT set the binary option) among others to generate the passphrase independently of SiriKali. This CLI tool should already be installed in your computer(it is in mine). You can also use openssl to generate the passphrase with something like below:
[1] http://manpages.ubuntu.com/manpages/xenial/en/man1/hmac256.1.html |
Implementations of key options are explained here: https://github.com/mhogomchungu/SiriKali/wiki/Frequently-Asked-Questions#40-what-does-different-key-options-means-in-the-dialog-for-creatingunlocking-volume |
Thanks! Already got it working. |
Version 1.2.5 of SiriKali(already released) has an option to display a password in the password dialog prompt and you can use this feature to see the generated key that will be passed to the backend. From CLI currently on this git version,you can get the password also by using "-s" option that enables the feature together with "-f" that takes a path to a keyfile. The password will be asked by a terminal prompt. Example of the above is below:
|
So as the title says, however I'm interested when the option of Key+KeyFile are used to create the volume. Does cryfs, securefs, gocryptfs, encfs or ecrypts support Key+KeyFile?
If a volume was created with SiriKali and Key+KeyFile can it be mounted with something else?
The text was updated successfully, but these errors were encountered: