#3 GPG Keychain Access Crash
Am 04.01.2004 um 15:48 schrieb Randall Wood:
Looking at the logs, it looks the programs are crashing while attempting to
read the user ids from one of the keys on your GPG keychain.
looking thru the keyring, the only "unusual" thing i can find are some keys with non-ascii
(escaped) Names:
pub 2048R/EF36997B 2001-01-27 H\xfc\x72bine von Pleuselspink huerbine@nym.alias.net
is one example (and a wellknown address...)
What version of gpg are you using?
1.2.4 because i use MacOSX 10.3.2.
You might want to try these commands from a terminal:
gpg --refresh-keys
refreshed a few keys but seems to be unreliable when using
gpg --refresh-keys --keyserver search.keyserver.net
gpg --fix-trustdb
% gpg --fix-trustdb
gpg: this command is not yet implemented.
gpg: A workaround is to use "--export-ownertrust", remove
gpg: the trustdb file and do an "--import-ownertrust".
and that's what i did.
gpg --list-keys
looks unchanged
and see what you get.
do you need the output?
Are you having similar errors with other gpg-based software, possibly when
encrypting to or verifying against a specific key?
I just tested GPGTools 1.1.6 and this Versions fails too. The older version (one that used gpg 1.0.7) worked fine.
A friend of mine (Michael Wagener) has the problem, that showing information about a key
using gpgkeys shows the information of a wrong key.
It looks like that the module which analyses gpg --list-keys fails
best regards,
Andreas
Andreas Franz nospam_webmail_2003@onlinehome.de
btw: my email-address -is- valid. I use "nospam" to fight the
"SWEN"-Worm....
Logfile of GPGTools
Logged In: YES
user_id=97331
Closed bug https://sourceforge.net/tracker/
index.php?func=detail&aid=870339&group_id=20789&atid=120789
which duplicates this bug. Am working on a tool to enumerate keys so
that keys causing problems can be found out. Hope that libGPGME 1.0
makes this problem a non-issue.