NicolasPetton / pass

A major mode for password-store
GNU General Public License v3.0
174 stars 22 forks source link

Some keybindings do not work if GPG keys stored in a removeable device #41

Closed doolio closed 10 months ago

doolio commented 4 years ago

This may well be an issue with password-store.el (@calancha) and/or auth-store-pass.el (@DamienCassou). I store my keys offline in a removeable device specifically a Trezor model T hardware wallet. So everytime I need to decrypt a password store gpg file to perform specific pass major-mode actions I have to confirm I want to decrypt the file on the trezor device.

error in process sentinel: password-store: exited abnormally with code 2

- I did not test the `o` binding beyond displaying the sub-menu.

I use EXWM too so it may be similar to #25.

FWIW, I'm using the following versions of these packages:

("auth-password-store" . "ff4940c647786914b3cbef69103d96a4ea334111") ("pass" . "919d8e3826d556433ab67d4ee21a509d209d1baa") ("password-store" . "98193d3bbb3538eda457d0db4ccccbcc4b04ce3d")


Thanks for your time.
doolio commented 4 years ago

I was able to get these bindings to work by changing the following switches in the trezor specific agent-program ~/.gnupg/trezor/run-agent.sh

--pin-entry-binding=pinentry-emacs --passphrase-entry-binary=pinentry-emacs

I still observe the following error as described above.

Error during redisplay: (jit-lock-function 1) signaled (invalid-function #<subr quote>)

I still have some other issues but I believe they are related to the trezor-agent.

cjauvin commented 4 years ago

I do not use any removable device and I'm also having the Error during redisplay: (jit-lock-function 12) signaled (invalid-function #<subr quote>) error, which prevents me from inserting any new password. I'm using Emacs 27, are you also, by any chance?

doolio commented 4 years ago

Yes, I recently upgraded to 27.1 and still see this error.

DamienCassou commented 10 months ago

This issue discusses a lot of problems, some of which seem to have been resolved. Should we close the issue and maybe open new, more specific, ones?

doolio commented 10 months ago

Yes, good idea.