Werner Koch wrote: > running gpg without an explicit "--default-key" is not suggested as you > don't have any control on what gpg views as its default key. When > adding --default-key it is not much work to also add an --encrypt-to.
It does work fine, though, if you have only one private key. I'd like to share gpg.conf between machines; apart from the key IDs, it seems entirely non-machine-specific. gpg doesn't seem to support any configuration file include mechanism that I could use to split configuration files. Do you have any other suggestion on how to make gpg.conf non-key-specific? - Josh Triplett
signature.asc
Description: OpenPGP digital signature
