Hey all, This might have been discussed, but I did look around and did not find any good points about coping with the poisoned keys. Without having to recompile the public ring that is.
1. First off: find out any poisoned keys. * https://dev.gnupg.org/T3972#127356 Daniel Kahn Gillmor @dkg wrote an awk script to list the keys along with their apparent size (largest at the end). The bigger ones are probably the poisoned ones. For me for instance: > 1424542 keyid: D2BB0D0165D0FD58 > 8203788 keyid: EE8192A6E443D6D8 > 15874931 keyid: DB1187B9DD5F693B These are CACert.Org's GPG certificate and two of Patrick Brunschwig's certificates. The CACert.Org certificate might be just big, not necessarily poisoned. 2. To clean a certificate from the unusable signatures: > gpg --edit-key DB1187B9DD5F693B clean save This took about 40 minutes on my laptop for the 15MB key. 3. After the bulk clean-up: > gpg --edit-key DB1187B9DD5F693B check clean save This was pretty quick. I do not know if there are any side effects from cleaning the keys this way. Please correct me if I did/wrote wrong. At least now I can read/write e-mails. _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
