<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Hi Robert.</div>
<div> </div>
<div>Found the file and I'll plug in your suggestion and run a test.</div>
<div> </div>
<div>Can I move that KBX file to the C:\Program Files\GnuPG folder for a more central location?</div>
<div> </div>
<div><img src="cid:C1EF611BE4DDD242B028BBE5AC35005C@namprd13.prod.outlook.com"> </div>
<div> </div>
<div>Rick</div>
<div> </div>
<div>-----Original Message-----<br>
From: Robert J. Hansen <rjh@sixdemonbag.org> <br>
Sent: Tuesday, December 17, 2019 9:31 AM<br>
To: Rick Rustad <rick.rustad@enavate.com><br>
Cc: gnupg-users@gnupg.org<br>
Subject: RE: GnuPG v2.2.17.22805 with StarksoftCryptographyOpenPGP</div>
<div> </div>
<div>On 2019-12-17 10:10, Rick Rustad wrote:</div>
<div>> So very glad you responded.</div>
<div> </div>
<div>We try to be helpful. We sometimes fail, but we try. :)</div>
<div> </div>
<div>> I see a bigger issue looming. If this customization I'm working on </div>
<div>> will be used by many people and thus the encryption and signature </div>
<div>> processing will be utilized by the same many people, is there a way to </div>
<div>> override or tell the command line argument to GnuPG to not be user </div>
<div>> specific?</div>
<div> </div>
<div>Yep. Use both "--no-default-keyring" and "--keyring". For instance:</div>
<div> </div>
<div>$ gpg --no-default-keyring --keyring \path\to\pubring.kbx --list-keys</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>> In one of my tests I replaced "--recipient" with "--default-recipient"</div>
<div>> but it had no affect, same error message.</div>
<div> </div>
<div>Yeah, that's expected and doesn't shed much light on the matter.</div>
<div> </div>
<div>ATTENTION: This email was sent to Enavate from an external source. Please be extra vigilant when replying, opening attachments or clicking links.</div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>