On Mon, Sep 11 2017, Daniel Kahn Gillmor wrote: > gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory > gpg: can't connect to the agent: No such file or directory > gpg: agent_genkey failed: No agent running > Key generation failed: No agent running > 2 dkg@sid:~$
Since I always had to use the agent, I never noticed. Sorry about that. > something fancier and more narrowly targeted, they could do something > like: > > Depends: gpg-agent, gpg > Recommends: gnupg I'd rather go for this route, and recommend gpg-agent from gpg, mentioning that secret key operations require at least the agent to be running in the description. > since i don't believe that pass has any need for network access > (dirmngr) or X.509 or CMS (gpgsm). But i don't know pass super well so > i can't guarantee that this is correct. pass doesn't fetch external keys. > I certainly don't want most users to have to think about which > specific packages they need to install. I'm actually happy that newer versions of gpg do not require dirmngr to be running anymore. When using gpg non-interactively, having services start-up unexpectedly (especially under systemd activation) is not something I'm pleased with. I remember I filed a bug report about the agent/dirmngr activation. I use gpg for batch unattended operations, but it looks like gpg is becoming more and more a tool for strictly interactive usage.
