rage
fails when pinentry-emacs
is installed AND the key is password protected.
If a pinentry binary is present rage uses it.
rage is a simple, modern, and secure file encryption tool, using the age format.
> echo "test" > test.txt
> nix shell nixpkgs#rage
> rage -R test-ed25519.pub test.txt -o test.txt.age
❯ rage -d -i test-ed25519 test.txt.age
** write key("test") password **
test
> nix shell nixpkgs#pinentry-emacs
> rage -d -i test-ed25519 test.txt.age
stat: No such file or directory
stat: No such file or directory
Error: No matching keys found
[ Did rage not do what you expected? Could an error be more useful? ]
[ Tell us: https://str4d.xyz/rage/report ]
pinentry-emacs
was installed as a system package, the ssh-key is password protected(
rage
only fails when pinentry-emacs
is used, ie. ssh key is password protected) and I have
no experience with rage
.
First, I have no idea what caused this error. Normally stat: No such file or directory
is a indication that a file/dir doesn't exist - but what/which file?.
nix run nixpkgs#rage -- -d -i test-ed25519 test.txt.age
stat: No such file or directory
stat: No such file or directory
Error: No matching keys found
[ Did rage not do what you expected? Could an error be more useful? ]
[ Tell us: https://str4d.xyz/rage/report
Let's make there's nothing in the enviroment that's causing the error (env -i env
shows that the enviroment is cleared)
❯ env -i nix run nixpkgs#rage -- -d -i test-ed25519 test.txt.age
Type passphrase for OpenSSH key 'test-ed25519':
test
Ok, let's figure out what wrong with the env