Patch for ca-dosign?

[Theo Van Dinter]

--jRHKVT23PllUwdXP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

I thought I'd send up a patch that I've been using on my box since finding
cabot last year.  The issue is that I have 2 full public/private key
pairs.  One is used, outwardly, for trust purposes only.  I sign people's
keys with it, and other people sign it.  The other key, which is setup
as the GPG "default-key" is the one I use in day-to-day communications,
expires, and is only signed by the first key so there's a trust path.

This works fine normally, except that ca-dosign calls gpg directly to
edit/sign the key, and doesn't pass the configured keyid to use for
signing, which leaves gpg to use the default-key which isn't the one I
want cabot to use.

So the question is: where should I send the patch?  Is there a bug
tracking system I can send it to?

Thanks! :)

--=20
Randomly Generated Tagline:
"Any similarity to person/persons now living to anyone or thing, dead or=20
 undead, is entirely accidental and just one more irrefutable proof of the=
=20
 paranormal."                  - From the 7th Guest

--jRHKVT23PllUwdXP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFA55t17tgKAJaXVyoRAi2BAKCzxP/O/fuMNff5CtMSTdNEW/YVrACffZoo
VHaspDoU6yXJzRqtNcpdVCE=
=P2vf
-----END PGP SIGNATURE-----

--jRHKVT23PllUwdXP--