On 20/03/2015 10: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 > . >
That worked fine. Deletion was a shade more complex as two old Thawtes keys had private keys, but all is now well. Thanks again, Regards, Bob _______________________________________________ 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
