On Tue, Oct 25, 2022 at 05:16:10PM +0200, Bernhard Reiter
wrote:
> Am Freitag 23 September 2022 18:19:42 schrieb Louis Holbrook via Gnupg-users:
> > - I would like to use pinentry-tty during my normal gpg cli operations.
> > - I am fine with using pinentry-curses in the mutt context
> >
> > Is t
It's not very bad in a curses environment, but I don't like that it
clears out my terminal when I use it from the command line, and I do
that a LOT.
On Tue, Oct 25, 2022 at 05:16:10PM +0200, Bernhard Reiter wrote:
> Am Freitag 23 September 2022 18:19:42 schrieb Louis Holbrook via Gnupg-users:
> >
Am Freitag 23 September 2022 18:19:42 schrieb Louis Holbrook via Gnupg-users:
> - I would like to use pinentry-tty during my normal gpg cli operations.
> - I am fine with using pinentry-curses in the mutt context
>
> Is there a way to do this?
FWIW: Probably not, as the pinentry is a configuration
Well, pinentry-tty is what I prefer for using gpg for all other
operations. Since I'm using the gpg-agent, there doesn't seem to be a way to
specify using an alternative just for mutt.
The only way I know to make that work with gpg cli is to have
--pinentry-mode set to loopback, and pinentry-progr
On Tue, 20 Sep 2022 16:56, Louis Holbrook said:
> I am using /usr/bin/pinentry-tty for password input, which in the
> interactive mode lets me paste a password from the terminal.
Please use pinentry-curses or, if you run in an xterm, better one of the
GUI pinentries. The pinentry-tty is a very d
Hey,
Not sure whether here or mutt list is the right place for this, but here
goes:
---
When encoutering a multipart/encrypted - application/pgp-encrypted file,
mutt asks le for a passphrase, but it does not register the input.
I am using /usr/bin/pinentry-tty for password input, which in the
i
