Problems with an expired key...

[L. Sassaman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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/options
> > > 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:
> 
> 1) By forcing the ID in .gnupg/options, I AM able to properly sign messages.
> 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).
> 
> --Chris

Set the "Encrypt-to" option in the .gnupg/options file.

And while you're fussing with config files, fix your email client not to
use PGP/MIME. :)	



__

L. Sassaman

System Administrator                |  "All of the chaos
Technology Consultant               |   Makes perfect sense..."
icq.. 10735603                      |
pgp.. finger://ns.quickie.net/rabbi |              --Joe Diffie



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: OpenPGP Encrypted Email Preferred.

iD8DBQE40C6CPYrxsgmsCmoRAmZsAKCilWIv6awyhAsIqtpeydVFXpt2AACeNzAv
xgIVYITHJDy6SDSRNczPf/k=
=f3n3
-----END PGP SIGNATURE-----