GnuPG v2.2.17.22805 with StarksoftCryptographyOpenPGP

Rick Rustad rick.rustad at
Tue Dec 17 16:54:09 CET 2019

Hi Robert.

Found the file and I'll plug in your suggestion and run a test.

Can I move that KBX file to the C:\Program Files\GnuPG folder for a more central location?


-----Original Message-----
From: Robert J. Hansen <rjh at>
Sent: Tuesday, December 17, 2019 9:31 AM
To: Rick Rustad <rick.rustad at>
Cc: gnupg-users at
Subject: RE: GnuPG v2.2.17.22805 with StarksoftCryptographyOpenPGP

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.

ATTENTION: This email was sent to Enavate from an external source. Please be extra vigilant when replying, opening attachments or clicking links.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 1.jpg
Type: image/jpeg
Size: 65694 bytes
Desc: Picture (Device Independent Bitmap) 1.jpg
URL: <>

More information about the Gnupg-users mailing list