Re: [pgpenvelope-users] Mailing list now on sourceforge.net

[Frank T. <ft...@ui...>]

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

L. Sassaman, at 23:38 on Sun, 6 Feb 2000, wrote:

> I have two keys with the same uid on my keyring. The first one is
> disabled... but when I try to encrypt mail to that address, PGPEnvelope
> still offers me that key (then GPG chokes on it). Any way to check and see
> if a key is disabled before presenting it in the list of possible
> encryption keys?

Currently, the method pgpenvelope is using to get key information is very
blunt, to say the least; it is just capturing the output of "gpg
- --list-keys".  Using this method, there is no way to sense if a key has
been disabled.  I've been putting it off, but given this scenario has
provided me with the 'push' to use the "--with-colons" options to grab the
data in a well-defined, parseable manner.  This will require a major
rewrite of the key handling of pgpenvelope, so it will take some time.
Look to see for such a design in a near-future version of pgpenvelope.

- -- 
Frank Tobin		http://www.neverending.org/~ftobin/

"To learn what is good and what is to be valued,
those truths which cannot be shaken or changed."  Myst: The Book of Atrus

OpenPGP:  4F86 3BBB A816 6F0A 340F  6003 56FF D10A 260C 4FA3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: pgpenvelope - http://www.uiuc.edu/ph/www/ftobin/resources.html

iEYEARECAAYFAjieebcACgkQVv/RCiYMT6P5RgCfajVc2GwllOrVtyJstfC7Lg7p
bQsAoIUtnOet2SMio1WdbNkqpSC9yLNT
=jcXZ
-----END PGP SIGNATURE-----