If you installed QSAam to the QSLite home directory, the program uses QSLite's gpg.conf. Should you decide to play around with it keep in mind that you'll be modifying gpg.conf for QSL as well.
Should you wish to modify the GPG configuration, this info describes how to make changes in gpg.conf so that they won't be overwritten by QSLite when it rewrites the file during the normal course of events.
QuickSilver uses the industry standard open-source OpenPGP software, GnuPG (GPG) to provide PGP related cryptographic services.
A mostly new configuration file is generated just before each PGP operation. Here's an example gpg.conf:
# QS maintains the values for keyring, secret-keyring, # and default-key. If you add or modify values ABOVE these # entries, do so with extreme care. Items added below these # will be deleted. no-greeting no-mdc-warning trust-model always no-default-keyring keyring C:\qs\pubring.pkr secret-keyring C:\qs\secring.skr default-key 0x67D0D303
The first time QSL runs GPG this file is created. After that, the file is read in and modified for the new PGP operation. To that end, everything starting with the keyring line is deleted. In the case above, after deletion the following fields remain:
# QS maintains the values for keyring, secret-keyring, # and default-key. If you add or modify values ABOVE these # entries, do so with extreme care. Items added below these # will be deleted. no-greeting no-mdc-warning trust-model always no-default-keyring
Then keyring is added again, along with secret-keyring, and default-key.
This system allows you to add or modify options in the section above keyring and they'll be preserved. For more info on all GPG options, see the file, gpg.man.txt. That file is located in QSL's doc\gpg sub-directory.
If you tinker with the config and you can't get GPG stable again, delete gpg.conf. QSL will create a new default file next time you use PGP.