[firstname.lastname@example.org: Re: [email@example.com: Bug#54067: mutt: incredibly slow signing/encrypting with gpg]]
wk at gnupg.org
Thu Jan 6 12:44:03 CET 2000
On Thu, 6 Jan 2000, Marco d'Itri wrote:
> From: David DeSimone <fox at rsn.hp.com>
> To: "Marco d'Itri" <md at linux.it>
> Cc: Mutt Wizards <mutt-dev at mutt.org>
> Subject: Re: [joey at varesearch.com: Bug#54067: mutt: incredibly slow signing/encrypting with gpg]
> Joey Hess <joey at varesearch.com> wrote:
> > /usr/bin/gpg --no-verbose --batch --with-colons --list-keys
> > This command takes a full 5 minutes to run on my PII-350. Which makes
> > sigining or encrypting mail in mutt intolerable.
Probably this is the first time it runs and you have a large pubring.
gpg builds it trust database and calculates the validity of each key.
I know that this takes much to long and we should redesign the whole
thing :-(. There are other problem with the old design: e.g. it does
not make sense to have a separate DB for the ownertrust values but add
local-only key signatures to the pubring.
If you use --fast-list-mode (GnuPG 1.0.1) the validity calculation is
suppressed. The problem with Mutt is that it displays all keys with
it's current key trust parameters and later uses --always-trust to
suppress the validation check when encrypting.
Werner Koch at guug.de www.gnupg.org keyid 621CC013
Boycott Amazon! - http://www.gnu.org/philosophy/amazon.html
More information about the Gnupg-devel