Problems with an expired key...

Christopher Smith
Wed, 15 Mar 2000 16:49:59 -0800

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

On Wed, Mar 15, 2000 at 04:44:38PM -0800, L. Sassaman wrote:
> On Wed, 15 Mar 2000, Christopher Smith wrote:
> > On Wed, Mar 15, 2000 at 02:44:56PM -0800, Christopher Smith wrote:
> > > On Wed, Mar 15, 2000 at 02:40:34PM -0800, L. Sassaman wrote:
> > > > Do you have the old key set as the default key in your .gnupg/optio=
> > > > file?
> > > Yup. I have partially fixed the problem by forcing my ID in mailcrypt,
> > > but I'd still like gpg to handle things correctly.
> > I need to clarify this:
> >=20
> > 1) By forcing the ID in .gnupg/options, I AM able to properly sign mess=
> > 2) However, if I want to send self-encrypted messages, I have to
> > specify the key ID. If I specify a user id, GPG wants to use my old,
> > expired public key. This despite the fact that it's disabled (indeed,
> > if I disable the old key, GPG exits with a failure if I try to encrypt
> > to my own user id).
> Set the "Encrypt-to" option in the .gnupg/options file.
Well, that did indeed fix it, although it is really only a work
around. Why can't GPG select the version of a public signature that
has not expired?
> And while you're fussing with config files, fix your email client not to
> use PGP/MIME. :)=09
Hey, I'd think that on this list of all places PGP/MIME would be well

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

Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see