> Yes it's a good idea... i'd also try to abstract the issue even more, > so if i manage to use gpg-agent in a way that doesn't involve pass, > (maybe asimmetrically signing/encrypting some files)
*decrypting > and the error > shows up again when invoking via stdbuf, than it'd be likely and > strictly an issue on gpg-agent and not pass... (shouldn't it?) > > Updates will follow... Well, using: stdbuf -oL gpg --use-agent --sign <file> works without errors retrieving the cached password from gpg-agent. I'd say the problem is not directly gpg-agent then... Anyways executing the command above, i noticed it asked me the passphrase via pinentry curses althogh it was already cached, because i used it few seconds before with pass, and i used it after just to be sure (obviously i have signed the test file with the same key pass uses to encrypt its password store). Now i don't know gpg-agent internals, but shouldn't it have used the already cached passphrase? Also the two pinentry dialog showed when using pass and when using gpg are slightly different in text and size. But maybe this is OT. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
