Menu

#304 Key Management 'Refresh All Public Keys' does nothing

fixed
nobody
None
1.7.0
Minor
24.5.0
2.0.25
All
1.8.0
nobody
2014-09-15
2014-08-14
No

Attempting to refresh all public keys in Key Management for 'keys.gnupg.net' does nothing (a dialog pops up but indicates no real progress), and never goes away. It doesn't look like any actual command is being triggered.

The same behaviour happens for other keyservers.

Originally I thought this was an issue with keys.gnupg.net, so reported here, but it turned out that the Enigmail command was resulting in no HTTP traffic whatsoever according to Wireshark!

Both gpg and gpg2 worked fine with --refresh-keys.

As requested enigdbug.txt is attached.

1 Attachments

Discussion

  • Ludwig Hügelschäfer

    There's no call for gnupg to refresh keys at all in the log. Did you issue the "refresh keys for all/selected keys" within this session?

    I also tried the server keys.gnupg.net. No problem at all.

     
  • Omega Weapon

    Omega Weapon - 2014-08-14

    Of course I did... this isn't new behaviour either.

    To change, I did 'Refresh Selected Public Keys' with my key selected, some further events:

    ===========================================================

    2014-08-14 21:13:56.371 [DEBUG] enigmailKeyManager.js: enigGetClipboard: got data
    2014-08-14 21:14:03.588 [DEBUG] enigmailCommon.jsm: setPref: keyserver, keys.gnupg.net, sks.mit.edu, hkp://keys.gnupg.net, pool.sks-keyservers.net, ldap://certserver.pgp.com, subkeys.pgp.net
    2014-08-14 21:14:03.670 [DEBUG] enigRetrieveProgress: onLoad
    2014-08-14 21:14:03.670 [DEBUG] enigmailCommon.jsm: receiveKey: 0x17D23C7DFDC2F38F
    2014-08-14 21:15:20.131 [DEBUG] enigmailKeyManager.js: enigGetClipboard:
    2014-08-14 21:15:20.131 [DEBUG] enigmailKeyManager.js: enigGetClipboard: got data
    2014-08-14 21:15:24.175 [DEBUG] enigmailKeyManager.js: enigGetClipboard:
    2014-08-14 21:15:24.175 [DEBUG] enigmailKeyManager.js: enigGetClipboard: got data
    2014-08-14 21:15:26.230 [DEBUG] enigRetrieveProgress: onLoad
    2014-08-14 21:15:26.230 [DEBUG] enigmailCommon.jsm: receiveKey: 0x17D23C7DFDC2F38F

    ===========================================================

    Same behaviour GUI-wise.

     
  • Ludwig Hügelschäfer

    Ok, I see, sorry. The call for gnupg to receive the keys is missing completely. This explains why you can't see http traffic. Which platform are you on? Can you see any entries in the Thunderbird Error Console? (Tools -> Error Console).

     
  • Omega Weapon

    Omega Weapon - 2014-08-15

    Debian Testing. Other than information messages about hardware acceleration, I get:

    ====================================================

    Timestamp: 15/08/14 17:52:17
    Error: SyntaxError: invalid quantifier
    Source File: resource://enigmail/enigmailCommon.jsm
    Line: 1700

    ====================================================

    Same error when refreshing a particular key, so this is probably it.

     
  • Ludwig Hügelschäfer

    Do you have a HTTP proxy configured? Do you have domains configured to use no proxy? Did you change one of those settings recently? Line 1700 in enigmailCommon.jsm is within a function to determine a valid proxy host name. Not sure why the failure occurs.

     
  • Omega Weapon

    Omega Weapon - 2014-08-15

    I do - proxy.omeganet (this works, and is used by my Firefox installation as well). Its not a recent change.

    No proxying for: localhost, 127.0.0.1, *.omeganet, 10.1.0.0/24

     
  • Omega Weapon

    Omega Weapon - 2014-08-15

    The following works (for reference):

    gpg --refresh-keys --keyserver keys.gnupg.net --keyserver-options http-proxy=http://proxy.omeganet:8888

     
  • Ludwig Hügelschäfer

    The problem is not with your settings themselves. Probably the processing of your settings cause a failure in enigmailCommon.jsm which might cause the failure of key lookups/refreshes from within Enigmail.

    We will look into this, but this will take some time.

     
  • Omega Weapon

    Omega Weapon - 2014-08-15

    OK - in the meantime gpg will do the job fine.

     
  • Ludwig Hügelschäfer

    Would you please try again with ".omeganet" instead of "*.omeganet" and tell if that works.

    (N.B. This would still be a bug, we must not fail for any user input)

    Thanks!

     
  • Patrick Brunschwig

    • status: open --> fixed
    • Fixed in version: --- --> 1.8.0
     
  • Patrick Brunschwig

    The problem was that *.domain.name broke our proxy handling.

    Bug fixed and committed to master.

     

Log in to post a comment.