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
Just leaving some notes here in case it's helpful for someone.
After upgrading my system from Fedora 40 to Fedora 41 (Kinoite) I couldn't open my tombs. I use pass-tomb in an Ubuntu distrobox.
pass open -v produced the following error:
...
. tomb . This tomb is a valid LUKS encrypted device.
. tomb . Cipher is "aes" mode "xts-plain64" hash "sha512"
. tomb [E] No valid password supplied.
[x] Error: Unable to open the password tomb.
Not sure why this started after the upgrade, but it seems to be related to tty for gpg.
Entering into the distrobox and running export GPG_TTY=$(tty) before opening the tomb made pass open finally work.
The text was updated successfully, but these errors were encountered:
you could try a prior version of pass-tomb to see if that's it
also Guix just upgraded to gnupg 2.4, so that may have something to do with it. is gpg working for you much at all right now?
when i encounter weird issues like this, strace can help to pinpoint the problem, but you need to be careful with it here, since it's going to record some sensitive data. it shouldn't dump decrypted data but ... actually idk it might, so delete tomb.strace and maybe ask around before you try it.
# list all of the syscalls made.
straice -o tomb.strace` -e %all pass open -v
Just leaving some notes here in case it's helpful for someone.
After upgrading my system from Fedora 40 to Fedora 41 (Kinoite) I couldn't open my tombs. I use pass-tomb in an Ubuntu distrobox.
pass open -v
produced the following error:Not sure why this started after the upgrade, but it seems to be related to tty for gpg.
Entering into the distrobox and running
export GPG_TTY=$(tty)
before opening the tomb madepass open
finally work.The text was updated successfully, but these errors were encountered: