Werner Koch wrote: > On Wed, 6 Jun 2007 22:14, [EMAIL PROTECTED] said: >> It does work fine, though, if you have only one private key. > > And as long as you don't accidently import another secret key.
True. >> 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? > > Using an environment variable for the default key? We would need to > implement this. And then also your suggestion ;-) That sounds like an interesting option to solve the split configuration problem. That would allow me to share gpg.conf, and put the default key ID in a machine-specific environment file (which I will probably need anyway). One other, somewhat more elegant possibility: how about allowing a list of key IDs for default-key, and selecting as the default key the first one with a private key available? That would allow a single configuration that said "If I have my secure private key, use that, otherwise use my somewhat-secure work key." encrypt-to-self would become even more important in this situation: it would tell gpg to encrypt to whichever key it uses as the default key. > Please file a bug report at bugs.gnupg.org if you really want that. Done. Issue 806 suggests accepting a list of key IDs for default-key, and issue 807 suggests the encrypt-to-self option. Thanks, Josh Triplett
signature.asc
Description: OpenPGP digital signature
