Like, I suspect, a lot of people, I have two keys with identical
key IDs, one of which is a 1024-bit RSA key that I no longer use.
Since I created it first, it's earlier in GnuPG's keyring, so key
selection by name and email address will generally always choose it.

Most Debian infrastructure commands have a way of persistently
configuring the actual key ID to use instead so that I can point
them at my newer key.  dcut takes the -k option, which works fine,
but there doesn't seem to be a way to persistently configure it with
either an environment variable or a configuration file.

I can just create a shell alias of dcut to dcut -k <keyid>, but it
would be nice if there were some place I could stick that in a
configuration file.

Hi Russ,

I think this option is already implemented since 1.4 with this commit:
http://anonscm.debian.org/gitweb/?p=collab-maint/dputng.git;a=commitdiff;h=047ea30199426bf7e3f455af67e24e495c64b38e

Luca Falavigna <dktrkranz@debian.org> writes:

Ah, I see what confused me.  default_keyid isn't supported in ~/.dput.cf.
It is supported in the new configuration syntax.

I'm not completely sure that I understand exactly how the new syntax
works, but it looks like should create a file named
~/.dput.d/profiles/DEFAULT.json with the contents:

    {
        "default_keyid": "D15D313882004173"
    }

Did I understand that correctly?

It looks like I have some work to do to rewrite my .dput.cf file into the
new format, since if the new format is richer, I may as well bite the
bullet and do a conversion rather than trying to continue to maintain
configurations in two different formats.