Skip to content
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

No valid password supplied #46

Open
fdesjardins opened this issue Dec 15, 2024 · 2 comments
Open

No valid password supplied #46

fdesjardins opened this issue Dec 15, 2024 · 2 comments

Comments

@fdesjardins
Copy link

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.

@Kabouik
Copy link

Kabouik commented Jan 24, 2025

I've got the same issue on Guix system. Unfortunately your workaround does not work for me.

Not having access to my password manager anymore is quite limiting. Any help would be very appreciated.

$ export GPG_TTY=$(tty)
$ echo $GPG_TTY
/dev/pts/8
$ pass open -v
…
  .  .tomb-real  .  This tomb is a valid LUKS encrypted device.
  .  .tomb-real  .  Cipher is "aes" mode "xts-plain64" hash "sha512"
  .  .tomb-real [E] No valid password supplied.
 [x] Error: Unable to open the password tomb.

@dcunited001
Copy link

dcunited001 commented Jan 24, 2025

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

ldd in case it's a linking issue

# check resolution of libs
ldd `which pass`

# sort dynamically linked libs for easier checking (this uses tabs)
ldd `which pass` | tr '	' ' ' | cut -f2,4 -d' ' | sort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants