-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>> 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/ iQGcBAEBCAAGBQJVDJiiAAoJEKGX32tq4e9Wb1wL/23MvGne7muHlOhRksem2h97 5qYEV8XHuSOLBF1yqYqlstDNhi332ekmuwl2PP0oZQaFO8FdlEEwlG+wLcZ9+8Kh 5n6j/W/4NVjpcw1u+2Sy/VRSvklUYCyM1Ye6moZycEY9yD6je5OVkWeDnj7oAcrF oAQkPFLI+H1xiod3vbwPUmJ4lD8Ho8Cl1KYytVAfnfiX9iHrlqYVCyArnsa+bgDE YtuAhtQkXJwxoxfKBrQWgHlTzsJmEfjkR7y4qCGZN/djQsUUN7Esvxrtd8x28TnO N0GAKRrEwDRej5OvMH3n2qK/bTbnyc//NvSdulmv/zKXDMFWMNh5A8S4bZyOfvMs 6LpMWpR5foPX47Z4rTKqsXYoX7OhaFs5hLKwzLzZ+xEGg8VfWK9WHHrUQ0TXxvF+ NkW0zfvU7CORkJl/JT/WlPLZQXs8Y9OnxilFyPnoLalKYSiXezbHCdhR/K7M3tC6 ldtBOIs9rkYTvCWykrW2brD/1o8gEuit51xDLCBi6A== =BSKV -----END PGP 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
