[Users] [Bug 3960] New: Sends unencrypted emails when encryption fails

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Fri Feb 9 09:34:39 CET 2018


http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3960

            Bug ID: 3960
           Summary: Sends unencrypted emails when encryption fails
    Classification: Unclassified
           Product: Claws Mail
           Version: 3.13.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: UI/Compose Window
          Assignee: users at lists.claws-mail.org
          Reporter: claws_bugzilla at gdr.name

When sending to one recipient, I'm getting the most unusual behavior: There's
some PGP error but Claws decides to send the email in plaintext anyway. 

The error is probably in my setup and I'm not really asking for help with this,
but it's a security problem that plain text email is being sent when it's not
expected. I would expect 

0. Privacy system = PGP Inline, Encrypt, not Sign
1. Getting an alert "Please note that attachments are not encrypted by the
PGP/Inline system, nor are email headers, like Subject."
2. Getting "This encryption key is not fully trusted.
If you choose to encrypt the message with this key, you don't
know for sure that it will go to the person you mean it to."
3. Getting an alert with a red X icon, title "Error", heading "Error" and text
"Couldn't encrypt the email: Unknown error", with only Close button.


Claws Mail version 3.13.2 from Ubuntu 16.04 repos. (BUT AS FAR AS I SEE THE
CODE IN HEAD IS NO DIFFERENT - SEE BELOW)

PGP/Inline plugin Version: 3.13.2

➜  ~ gpg2 --version
gpg (GnuPG) 2.1.11
libgcrypt 1.6.5
...
➜  ~ gpg --version
gpg (GnuPG) 1.4.20
...

Could it be that this branch in code should return a negative number to prevent
the message from sending?

http://git.claws-mail.org/?p=claws.git;a=blob;f=src/compose.c;h=ae5cd90e89b68b0056553d441d851b0ced5b5d78;hb=HEAD#l5903

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Users mailing list