Hi Daniel, all, Am 2015-01-21 um 17:35 schrieb Daniel Kahn Gillmor:
> It sounds to me like these are OpenPGPv3 ("PGP-2") keys, which are
> probably due to be replaced. Can you try stashing those keys in a
> separate file, and then removing them from your public keyring?
> something like (where $key1,$key2, and $key3 are the keyids of these old
> keys):
>
> gpg --export-options export-local --armor --export $key1 $key2 $key3 >
> openpgpv3.backup
> gpg --delete-key $key1 $key2 $key3
>
> Then does the gpg2 --list-keys command return 2 as well?
OK, I removed the 5 keys that had 0000 fingerprints in the gpg2 listing
from my keyring and now gpg2 --list-keys works without error. I also
checked it in enigmail and it also works here now.
> I don't think that simply having v3 keys in your keyring should make gpg
> --list-keys return a non-zero value, but i'd like to know if it does.
Well, it looks like it does. It was complaining about MD5
hashes/fingerprints, but I think the behavior is not user friendly :( I
get the thing about not using MD5 anymore, but the way gpg2 works now is
that it definitely breaks things.
> Also, if you're using these packages from debian, what version of the
> debian packages are you running (different versions have different
> patches applied)? you can see that with:
Debian version:
gnupg: 1.4.18-6
gnupg2: 2.0.26-4
Regards,
--
j.hofmüller
We are all idiots with deadlines. - Mike West
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
