On Sun, Aug 26, 2007 at 05:57:06PM +0200, Rémi Laurent wrote: > $ gpg > gpg: directory `/home/foobar/.gnupg' created > gpg: keyring `/home/foobar/.gnupg/secring.gpg' created > gpg: keyring `/home/foobar/.gnupg/pubring.gpg' created > > # Getting Peter Palfrader key > $ gpg --keyserver pgp.surfnet.nl --recv-keys 94C09C7F > > # Refreshing pub keyring from pgp.mit.edu > $ gpg --refresh-keys --keyserver pgp.mit.edu > > # after a few seconds CPU usage raises to 100% > 9344 foobar 25 0 6492 3140 1188 R 100 0.3 0:48.35 gpg > # after 15 minutes, still the same, no timeout or any other error > 9344 foobar 25 0 6492 3140 1188 R 100 0.3 15:02.65 gpg
The issue is that pgp.mit.edu is slightly corrupting keys. GPG needs to decorrupt the key on import, but the algorithm for doing that is not very efficient. It will actually finish and do the right thing if you wait long enough (it can take hours on a slow machine). 1.4.8 (not yet released) has a much faster implementation that can do it in less than a minute. David
