On Sat, 15 Oct 2022 12:50, Robert J. Hansen said:
> Because GnuPG 2.x already starts the daemon. It should be running by
> the time you finish logging into your system.
Further the gpg-agent is responsible to compute the iteration count for
our KDF. That takes at least 100ms and thus either a
why can't gpg accept passphrase in the terminal?
Depending on how you invoke GnuPG, it can. It supports a lot of
different ways of providing the passphrase.
The one that might work best for your purposes is to put the passphrase
in a file, passphrase.txt, and then invoke GnuPG like this:
> On 15/10/2022 14.36, Robert J. Hansen via Gnupg-users wrote:
Why does gpg-agent interject itself into symmetric encryption at all?
Where in that command line do you specify a passphrase?
You don't.
gpg-agent is getting fired up in order to ask you what passphrase to use
for the symmetric
Why does gpg-agent interject itself into symmetric encryption at all?
Where in that command line do you specify a passphrase?
You don't.
gpg-agent is getting fired up in order to ask you what passphrase to use
for the symmetric encryption.
___
gpg: symmetric encryption of '[stdin]' failed: Operation cancelled
The same command works when I change symmetric to public key encryption:
tar --zstd -cf - zz/ | gpg -e -o /tmp/zz.tar.zstd.gpg
Why does gpg-agent interject itself into symmetric encryption at all?
What role does it want to play
