Menu

Can't sign emails - and decrypt if automatic signing

GNUbahn
2017-05-05
2017-05-18
  • GNUbahn

    GNUbahn - 2017-05-05

    I have searched for this issue but found no entries.

    Recently - and I can think of no changes in system or settings - Enigmail has failed to decrypt messages that have been decrypted earlier.

    I also couldn't send encrypted messages.

    But trial and error I have figured out that the problem is only there when signing is on. If signing is off, I can decrypt and send encrypted messages.

    Is this a known issue and is there a known solution?

     
  • Patrick Brunschwig

    Which version of GnuPG do you run? Did you maybe switch from GnuPG 2.0 to 2.1 or vice versa?

     
  • GNUbahn

    GNUbahn - 2017-05-08

    I am not sure. How do I know?

     
  • GNUbahn

    GNUbahn - 2017-05-09

    gpg2 --version gave me

    gpg (GnuPG) 2.1.11

    But I don't know if or when I may have upgraded it.

     
  • Patrick Brunschwig

    I would think that there is an issue with your GnuPG settings. Does Enigmail print some kind of error message other than "can't decrypt"?

     
  • GNUbahn

    GNUbahn - 2017-05-10

    I get this message:

    Enigmail Security Info Error - no matching private/secret key found to decrypt message gpg: afkryptering mislykkedes: Ingen hemmelig nøgle Note: The message is encrypted for the following User ID's / Keys: (followed by fingerprints of me and the sender)

     
  • GNUbahn

    GNUbahn - 2017-05-10

    Sorry, some is in Danish.

    "afkryptering mislykkedes: ingen hemmelig nøgle" means "decryption failed: No secret key"

     
  • GNUbahn

    GNUbahn - 2017-05-10

    Here is my debug log

     
  • Ludwig Hügelschäfer

    You're suffering from some major misbehaviour of GnuPG, maybe caused from a setup or installation error. The log says:

    gpg: waiting for lock (held by 7205) ...
    (...)
    gpg: waiting for lock (held by 7215) ...
    

    and then:

    "IPC-forbindelseskald mislykkedes"
    

    this means: "IPC connect call failed". You'd have to find out which process(es) interfere(s). In this case the PID of the interfering process is printed by GnuPG. You'd have to do this immediately after you see these messages in the Enigmail debug log.

    You are not by chance running a gpg-agent from a different version than the gpg executable or two gpg-agents (under the same user) simultaneously?

     
  • GNUbahn

    GNUbahn - 2017-05-10

    Thanks a lot for your efforts.

    I don't understand the technical stuff, but could this have to do with a chance of booting firmware?

    I must admit, that I have no idea as to whether I am "running a gpg-agent from a different version than the gpg executable or two gpg-agents (under the same user) simultaneously"

    How can I check that?

     
  • Ludwig Hügelschäfer

    No, this is most probably not related to booting firmware.

    To check whether more than one gpg-agent is probably easy, but using GUI it depends on the window manager you are running.

    On the command line:

    ps -A | grep gpg-agent
    

    This lists all gpg-agent processes (and will catch the grep command, too). So, if you get 2 lines, all is ok. If else, please post the output here for help.

     
  • Patrick Brunschwig

    please kill all gpg processes and delete any lock files in ~/.gnupg (they are probably hidden).

     
  • GNUbahn

    GNUbahn - 2017-05-18

    I was working on Trisquel 8.0, which is an unstable OS release. For other reasons I have downgrade to Trisquel 7.0, which is stable. I have had enigmail work with unstable OS-version and I still don't know what went wrong. But now it apparently works again.

    Still - after downgrading - I tried to

    ps -A | grep gpg-agent

    This gives me no output!

     
  • Patrick Brunschwig

    I said "gpg", not gpg-agent, i.e. "ps -A | grep gpg"

     
  • GNUbahn

    GNUbahn - 2017-05-18

    I was just following Ludwig's suggestion.

    ps -A | grep gpg

    gives me no output too

     
  • GNUbahn

    GNUbahn - 2017-05-18

    Is that weird?

     
  • Patrick Brunschwig

    I would think that something with your GnuPG setup is wrong. It looks like gpg cannot start gpg-agent. This may be due to a misconfiguration in gpg-agent or something else. Even though if it doesn't fit 100%, I would recommend you follow our troubleshooting guide for fixing issue with gpg-agent:
    https://www.enigmail.net/index.php/en/faq-en?view=topic&id=14 (section "Resolving issues with GnuPG 2.x and gpg-agent")

     
  • GNUbahn

    GNUbahn - 2017-05-21

    Thanks.

    I guess the actual issue will remain a mystery. But thanks a lot for your efforts. I'll see to the troubleshooting guide. If I have further issues, I'll be back.

     

Log in to post a comment.