Sorry for going off list and messing everybody up. Now I disserve
punishment. Sorry for the html too.
-------- Forwarded Message --------
Subject: Re: Newbie question.
Date: Sat, 11 Jul 2020 12:07:17 -0700
From: Ayoub Misherghi <[email protected]>
To: Peter Lebbing <[email protected]>
On 7/11/2020 11:30 AM, Peter Lebbing wrote:
Hi,
On 11/07/2020 19:58, Ayoub Misherghi wrote:
ayoub@vboxpwfl:~/sentry/trunk$ cat ~/.gnupg/gpg.conf
batch
pinentry-mode loopback
Ah yes. Those two options have no place in your gpg.conf. They are
options that you might want to specify as part of the command line on
occasion, but unless you have a very unusual setup they should not be
there. You should remove both. The pinentry-mode is probably what is
preventing you being asked for the passphrase.
My current intended usage is in non-interactive mode, completely.
I can remove them from the gpg.conf but I would have to issue them
every time. My understanding is that non-interactive mode requires
those commands.
expert
I'd recommend dropping this as well.
I selected "expert" mode because I am using ED2599 incrpytion that is
available only in this mode (I know, I am newbie)
#--passphrase-file file
#passphrase-file /home/ayoub/.gnupg/output.png
These commented out lines are probably why the pinentry-mode line was
there in the first place. Do you know why these lines, both the
uncommented and the commented ones, are in your gpg.conf?
All the config lines I showed are in my user config.
A few days ago, my set up, which is still in development phase,
worked until my short lived gpg keys expired. I fell in deep ***** when
I created new keys. It all worked, with the passphrase-file option and
without,
before I fell. Can you pull this dumb newbie out?
HTH,
Peter.
_______________________________________________
Gnupg-users mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gnupg-users
