On 03/20/2015 06:01 PM, Olav Seyfarth wrote: > >>> installed GnupG 2.0.27, via Gpg4Win 2.2.4 > >> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5. > >> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf > > Is there a method to search for such keys? > > I definitely *don't know whether this is correct*, but what I did is > > gpg --list-key 0x00000000000000000000000000000000 > This, in my case, *seemes* to list all affected keys. Don't ask me why. > I stumbled upon it while I got displayed keys with FPR all zero... > > I exported these keys to be able to roll back ... > > gpg --export 0x00000000000000000000000000000000 > md5_keys.gpg > > ... and deleted them manually by executing this as long as it still > found some: > > gpg --delete-keys 0x00000000000000000000000000000000 > > After that cleanup, I had no more errors even without > allow-weak-digest-algos . > > Olav > -- > The Enigmail Project - OpenPGP Email Security For Mozilla Applications > > _______________________________________________ > 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 > >
I got no keys but probably because I had done a manual scan in Kleopatra which will show the hash if you hover over a key. However, I am still getting a gpa error. Here it is: The GPGME library returned an unexpected error at keytable.c:150. The error was: Unsupported certificate This is either an installation problem or a bug in GPA. GPA will now try to recover from this error. Googling this suggests it may be a conflict between gnome-agent and the gpa-agent. I am running Ubuntu 14.10.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
