Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I have signed a friend's key and revoced the signature. After that I signed the key several times again but GPA and Enigmail list all of the keys as revoced.
The key is working though, so GnuPG handles it right but the Frontends fail to interpret it correctly.
I have checked this behavior on three different computers and every time it failed to display it correctly. After using the "clear" command everything gets corrected and the Frontends display correct information.
Of course I can share the key with you so that you can try it yourself: http://subset.pool.sks-keyservers.net:11371/pks/lookup?op=vindex&search=0x3B0F32018B87DFD3
Just import the 2 keys and see what happens.
I'm not sure if this is really an Enigmail issue but at least the code it is based on is not working correctly in this case.
PS: I use Gpg4win but a nice user who uses Linux already checked it with Enigmail and he had the same bug.
Do you mean that Enigmail (and GPA, which is out of scope here) lists your signature as revoked, or does it list the complete key as revoked?
It lists every signature as revoked. Valid signatures that are created after revsig are also marked as revoked. I just mentioned GPA to point out that it is not an Enigmail-only problem. Maybe some code that both frontends are based on is wrong.
PS: I wrote "clear" in the original post, I mean "clean" ofc.
GPA and Enigmail do not share any code.
I created [bugs:#171] for this.
Thanks for creating the bug report :)
When do you guess it will be fixed?
PS: It could be helpful to create a bug report for the GPA developers too, since they seem to have the same bug.
I (or whoever will fix the bug) will mark the bug fixed once this is done. I cannot predict when I will fix something.
Concerning GPA: feel free to report the bug to them...