On 27/07/2020 22:53, Ayoub Misherghi wrote:
> With API I mean something like GPGME.
It seems to me that including options in gpg.conf that GPGME does not
expect people to put there might throw it out of whack.
> 1) It is preferable to have "--batch" on command line even in
> unattended
With API I mean something like GPGME.
This is what came across to me:
1) It is preferable to have "--batch" on command line even in unattended
operation; and not in the gpg.conf file?
2) --pinentry-mode when needed goes in gpg.conf
3) --allow-loopback-pinentry when needed goes in
The same thing happens when I give the option --no-batch on the command
line.
The problem seems to have gone away when I moved the config option
inentry-mode loopback
to the $HOME/.gnupg/gpg.conf from the $HOME/.ngupg/gpg-agent.conf
In the final version when development ends, I am
On 27/07/2020 20:56, Ayoub Misherghi wrote:
> The same thing happens when I give the option --no-batch on the
> command line.
But that only passes --no-batch to gpg, not to gpg-agent. Werner said
you shouldn't put these options in your .conf-files. Please just include
--batch on the command line
On 27/07/2020 11:17, Werner Koch wrote:
> of the "batch" option. This option should in general not be used for
> gpg-agent.
Which, by the way, is documented well in the man page gpg-agent(1):
--batch
Don't invoke a pinentry or do any other thing requiring human
On Sun, 26 Jul 2020 13:25, Ayoub Misherghi said:
> I am not asked for pass phrase.
Right; that is because:
> # Lines uncommented in $HOME/.gnupg/gpg-agent.conf
> log-file $HOME/gpg-log.txt
> # The same thing happens when I comment this line out
> allow-loopback-pinentry
>
> batch
of the "batch"
I am not asked for pass phrase.
The following lines show you what I have in the ".conf-file"
###
###
#
# Lines uncommented in $HOME/.gnupg/gpg-agent.conf
log-file $HOME/gpg-log.txt
# The same thing happens
On 20/07/2020 20:25, Ayoub Misherghi via Gnupg-users wrote:
> gpg: decryption failed: No secret key
Are your gpg.conf and gpg-agent.conf (or let's just say any .conf-file
in your GnuPG home, ~/.gnupg) empty? Do you get a pinentry popup asking
for a passphrase?
Peter.
--
I use the GNU Privacy
ayoub@vboxpwfl:~/testdir$ ls
textfile
ayoub@vboxpwfl:~/testdir$ gpg -r develop1 -e textfile
ayoub@vboxpwfl:~/testdir$ ls
textfile textfile.gpg
ayoub@vboxpwfl:~/testdir$ gpg -u develop1 -o textfile.dcr -d textfile.gpg
gpg: encrypted with 256-bit ECDH key, ID 367BD2210D4E904D, created
