Menu

1.7.2 encrypts emails to people whose keys I don't have

2014-09-29
2014-11-23
  • Andrzej Godziuk

    Andrzej Godziuk - 2014-09-29

    TLDR: enigmail sends emails encrypted only with my own keys to people not in keyring

    After one of the last upgrades - not sure if it started at 1.7.2 or one of the previous upgrades - my clients started complaining about "attachments they cannot open".

    Enigmail started sending encrypted emails to people who are not in my keyring, who don't even know what PGP is. The emails are encrypted with my own keys only.

    I think that manually forcing not to encrypt helps with this problem but it doesn't happen all the time, so it's hard to tell.

    One of the recipients had a per-recipient rule telling enigmail to "NEVER" sign, encrypt or send PGP/MIME (because he was confused by attachments). He got encrypted emails nevertheless.

    TB 24.6.0
    EM 1.7.2
    GPG 1.4.14
    linux 3.11.0-26-generic

     
  • Ludwig Hügelschäfer

    Please try with a nightly build (https://www.enigmail.net/download/nightly.php) and see if this fixes things for you. Thanks!

     
  • Stefan Kurtz

    Stefan Kurtz - 2014-11-23

    I have the same issue. 'Encrypt' and 'sign' is on by default. Usually, if no key is present for recipient Enigmail simply ignored encryption and signing. But now (since 1.7.2 i guess) it opens a window to choose a key (that is not available).

    I've preconfigured this scenario on some other peoples systems (as they are not able to configure it themselves) and they told me their Thunderbird is sending encrypted messages to people without GPG now as well. Its possible that they wildly choose any key on the dialog though. But usually that dialog shouldn't come up in the first place (and it worked for years indeed. It just changed with one of the latest Enigmail versions).

    The workaround currently is to manually disable encryption/signing by clicking the icons on the bottom right during email composing.

    The latest nightly (1.8a1pre) didn't help here. I hope we can get the old behavior back.

    TB 31.2.0
    Win7

     

Log in to post a comment.

MongoDB Logo MongoDB