GnuPG v2.2.17.22805 with StarksoftCryptographyOpenPGP

Robert J. Hansen rjh at sixdemonbag.org
Tue Dec 17 16:31:16 CET 2019

On 2019-12-17 10:10, Rick Rustad wrote:
> So very glad you responded.

We try to be helpful.  We sometimes fail, but we try.  :)

> I see a bigger issue looming. If this customization I'm working on
> will be used by many people and thus the encryption and signature
> processing will be utilized by the same many people, is there a way to
> override or tell the command line argument to GnuPG to not be user
> specific?

Yep.  Use both "--no-default-keyring" and "--keyring".  For instance:

\$ gpg --no-default-keyring --keyring \path\to\pubring.kbx --list-keys

However, as of GnuPG 2.2 you can no longer specify private keys this
way.  There used to be an option, "--secret-keyring", which was used
just like "--keyring", but it's obsolete and now does nothing.

> In one of my tests I replaced "--recipient" with "--default-recipient"
> but it had no affect, same error message.

Yeah, that's expected and doesn't shed much light on the matter.