-
Notifications
You must be signed in to change notification settings - Fork 50
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
Transferring vault to a different machine #60
Comments
@hrishikeshrt copying the directory is the correct way to migrate |
Installation is correct (or at least I feel so, because I can have a local vault on both the systems, but if I transfer one To elaborate, Transfer Both systems are Edit: I updated the python version, and did not make a difference. |
Okay, it seems like the version of apt package Still, I feel like this was somewhat unexpected behaviour, potentially breaking vault across versions without any clear indication of why (since no error is thrown, just key isn't accepted). I am wondering if it's a good idea to note the system's On further reading, it seems like newer versions can open older databases. More about the incompatibility and workarounds mentioned here: https://www.zetetic.net/blog/2018/11/30/sqlcipher-400-release/ in the Compatibility section. |
Is it possible to transfer the vault to a different machine? I tried copying my
~/.vault
directory, however on a new machine it does not accept the master keyThe text was updated successfully, but these errors were encountered: