#310 Wrong display when gnupg auto retrieves keys

[Ludwig Hügelschäfer]

Please refer to mailing list post and subsequent private communication of debug information.

Obviously Enigmail is confused when gnupg auto retrieves missing keys when verifying signed messages (keyserver-options auto-key-retrieve in gpg.conf). Enigmail does not display the key in "Enigmail Security Info" and keymanager, although it has just been added to the keyring by gnupg.

[Ludwig Hügelschäfer]

When trying to access "View key properties", the JS-debugger says "** Error in file resource://enigmail/commonFuncs.jsm, line 619:
TypeError: keyListObj.keyList[keyId] is undefined"

[Ludwig Hügelschäfer]

Thoughts: Of course the newly introduced key is not yet visible in keyList[keyId], because we didn't reload the key cache. Should we do this before we display the verification info? This would be quite a performance killer for large keyrings...

[Patrick Brunschwig]

I'm pretty sure that GnuPG issues some message when downloading a key. We should detect that message and invalidate the key cache subsequently.

[Ludwig Hügelschäfer]

Yep, was also my thought some minutes ago when doing the dishes ;-) Will look for it in my debug log, I've enabled the same option as Philip and already got a hit.

[Ludwig Hügelschäfer]

Gnupg issues, I think on status-fd:

[GNUPG:] IMPORTED <some key="" information="">
[GNUPG:] IMPORT_OK 1 <key-fp></key-fp></some>

This is done when verifying a signed mail and the key was not available before. We should detect this and reload the key cache then. I'll experiment with this..

[Ludwig Hügelschäfer]

I cannot reproduce this any more. Even high stress on gpg in the background (like on my first sight importing keys did trigger check-trustdb) did not cause Enigmail to fail again.