[kmail2] [Bug 324963] New: general error on sending GPG encrypted mail after telling KMail to use untrusted key

[Martin Steigerwald]

https://bugs.kde.org/show_bug.cgi?id=324963

            Bug ID: 324963
           Summary: general error on sending GPG encrypted mail after
                    telling KMail to use untrusted key
    Classification: Unclassified
           Product: kmail2
           Version: 4.10.5
          Platform: Debian unstable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: crypto
          Assignee: kdepim-bugs at kde.org
          Reporter: Martin at Lichtvoll.de

Since "[Bug 44699] can't encrypt with gpg if the receiver's key is not signed"
is fixed, KMail allows to send mails to untrusted keys. This worked for quite
some time.

But recently I needed to send to untrusted key again and after confirming to
KMail that I want to use that untrusted key, entered the passphrase I got a
general error message that doesn´t tell much about the cause of the error.

Setting the key trust to fully trusted makes KMail sign and encrypt the mail
just fine.

This has security implications as it user can only work-around it by setting a
key to trusted they may not have had a chance to verify yet.

This might be a duplicate of

Bug 322708 - kmail should allow encrypting mails with keys of unknown/zero
trust 

but since this bug doesn´t contain any detailed information, I don´t know for
sure.

Reproducible: Always

Steps to Reproduce:
1. Sign and encrypt mail to a key that you do not fully trust.
2. Tell KMail to use that key nonetheless.
3. Enter your GPG key passphrase.
Actual Results:  
"Fehler beim Erstellen der Nachricht: Allgemeiner Fehler"

translated: "Error while creating mail: General error"

Expected Results:  
1) Sending to uncrypted mails works.

2) Any occurence of "general error" is replaced by an error message that is
more descriptive than that (I can file another bug report for that one if
needed)

martin at merkaba:~> apt-show-versions | egrep "(kmail|akonadi|gpg|gnupg)"
akonadi-backend-mysql:all/unknown 1.9.2-2 uptodate
akonadi-backend-sqlite:amd64/unknown 1.9.2-2+b1 uptodate
akonadi-server:amd64/unknown 1.9.2-2+b1 uptodate
akonadiconsole:amd64/unknown 4:4.10.5-2 uptodate
gnupg:amd64/unknown 1.4.14-1 uptodate
gnupg-agent:amd64/unknown 2.0.21-2 uptodate
gnupg2:amd64/unknown 2.0.21-2 uptodate
gpgsm:amd64/unknown 2.0.21-2 uptodate
gpgv:amd64/unknown 1.4.14-1 uptodate
kgpg:amd64/unknown 4:4.10.5-1 uptodate
kmail:amd64/unknown 4:4.10.5-2 uptodate
libakonadi-calendar4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-contact4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-kabc4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-kcal4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-kde4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-kmime4:amd64/unknown 4:4.10.5-1 uptodate
libakonadi-notes4:amd64/unknown 4:4.10.5-1 uptodate
libakonadiprotocolinternals1:amd64/unknown 1.9.2-2+b1 uptodate
libgnupg-interface-perl:all/unknown 0.46-3 uptodate
libgpg-error-dev:amd64/unknown 1.12-0.2 uptodate
libgpg-error0:amd64/unknown 1.12-0.2 uptodate
libgpgme++2:amd64/unknown 4:4.10.5-1 uptodate
libgpgme11:amd64/unknown 1.4.3-0.1 uptodate
libgpgme11-dev:amd64/unknown 1.4.3-0.1 uptodate
libqgpgme1:amd64/unknown 4:4.10.5-1 uptodate
python-gpgme:amd64/unknown 0.2-3 uptodate

(this are all from Debian Unstable, dunno why apt-show-versions doesn´t detect
it correctly)

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