From: Werner Koch <wk@gnupg.org>
To: ding@gnus.org
Subject: Re: epg and expired recipient keys
Date: Sat, 24 Feb 2007 17:00:50 +0100 [thread overview]
Message-ID: <87649ro899.fsf@wheatstone.g10code.de> (raw)
In-Reply-To: <x61wkh6n8i.fsf@aix.cs.uni-magdeburg.de> (Michael Piotrowski's message of "Fri\, 23 Feb 2007 14\:02\:21 +0100")
On Fri, 23 Feb 2007 14:02, mxp@dynalabs.de said:
> GnuPG automatically selects the right key to use, and avoids the
> expired ones.
>
> If this is a bug in epg, I'd think that someone must have run into it
> before--or could this be a local problem?
I had the same problem and discussed this with Ueno. The reason is
that epg uses --list-keys to get a list of macthing recinpients and
picks the first one. This is obviously not correct, as it should skip
all revoked and expired keys.
However, as this is a general problem I am thinking about adding a new
list mode which selects a useful key the same way gpg does when called
directly with -r. I have not come to a conclusion as there are valid
reasons for MUAs to do their own selection. For example a MUA might
keep a list of former contacts and use a fingerpritn directly to
select a key.
Salam-Shalom,
Werner
next prev parent reply other threads:[~2007-02-24 16:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 13:02 Michael Piotrowski
2007-02-24 16:00 ` Werner Koch [this message]
2007-02-26 10:37 ` Michael Piotrowski
[not found] ` <smutzxbtsam.fsf@linuxpal.mit.edu>
2007-02-26 12:23 ` Werner Koch
2007-02-26 12:49 ` Daiki Ueno
2007-02-26 14:31 ` Werner Koch
2007-02-27 11:23 ` Michael Piotrowski
2007-02-28 22:23 ` Daiki Ueno
2007-03-06 2:19 ` Wolfram Fenske
2007-03-06 4:29 ` Katsumi Yamaoka
2007-03-06 9:41 ` Wolfram Fenske
2007-03-07 19:19 ` Miles Bader
2007-03-07 19:25 ` Miles Bader
2007-03-08 1:06 ` dolist vs. while-loop (was Re: epg and expired recipient keys) Katsumi Yamaoka
2007-03-08 14:55 ` Miles Bader
2007-03-06 4:40 ` epg and expired recipient keys Daiki Ueno
2007-03-06 9:37 ` Wolfram Fenske
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87649ro899.fsf@wheatstone.g10code.de \
--to=wk@gnupg.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).