You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set the key_path attribute to a file containing an Atuin key in plain text. When loging to Atuin using atuin login -u ..., and not providing any key path with -k, I expected the key file provided in the config to be read by Atuin.
(I am using NixOS, so the key_path attribute is set by Nix in my case)
I couldn't find in the docs if the encryption key has to be stored in plain text.
What happened?
When setting the key_path attribute to a file containing an Atuin key in plain text, the following error is triggered:
Error: could not load encryption key
Caused by:
0: encryption key is not a valid base64 encoding
1: Invalid symbol 32, offset 4.
Location:
crates/atuin-client/src/encryption.rs:88:10
Here is the throwaway key generated by Atuin to reproduce the issue:
What did you expect to happen?
Hello,
I set the
key_path
attribute to a file containing an Atuin key in plain text. When loging to Atuin usingatuin login -u ...
, and not providing any key path with-k
, I expected the key file provided in the config to be read by Atuin.(I am using NixOS, so the
key_path
attribute is set by Nix in my case)I couldn't find in the docs if the encryption key has to be stored in plain text.
What happened?
When setting the
key_path
attribute to a file containing an Atuin key in plain text, the following error is triggered:Here is the throwaway key generated by Atuin to reproduce the issue:
throwaway_key.txt
Is the encryption key expected to be base64-encoded?
Atuin doctor output
The text was updated successfully, but these errors were encountered: