Bug 395085 - Signature of email with attachment is shown as invalid in Evolution
Summary: Signature of email with attachment is shown as invalid in Evolution
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 5.7.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-06 13:26 UTC by quazgar
Modified: 2023-01-01 05:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Sample mail, seems to work for KMail, fails for Evolution. (3.75 KB, application/mbox)
2018-06-06 13:26 UTC, quazgar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description quazgar 2018-06-06 13:26:08 UTC
Created attachment 113114 [details]
Sample mail, seems to work for KMail, fails for Evolution.

When sending an email with an attachment, its signature is shown as invalid by Evolution.

See the attached example mbox file.  It can be opened in KMail and KMail shows a valid signature, but when opened with evolution, the signature is said to be wrong.  This behavior will also be filed as a bug for Evolution, but I want to make sure that there are no open MIME-related issues with the message composition.
Comment 1 quazgar 2018-06-06 13:28:12 UTC
Evolution bug: https://gitlab.gnome.org/GNOME/evolution/issues/11
Comment 2 quazgar 2018-06-07 16:18:36 UTC
Could it be that the problem is on KMail's side?

- KMail does not strip trailing space.
- As per https://gitlab.gnome.org/GNOME/evolution-data-server/issues/4#note_234216, Evolution by default strips trailing whitespaces.

If I read https://tools.ietf.org/html/rfc3156, page 5, bullet point (4) correctly, "any trailing whitespace MUST then be removed from the signed material" before calculating the signature.

I am not accustomed enough with MIME messages and transfer encodings though to tell if there is no exception to the rule here ;-)
Comment 3 Justin Zobel 2022-11-26 00:14:06 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 John Apple II 2022-12-02 02:30:01 UTC
I'll add that I'm having this issue currently - but the odd thing is it occurs when I send an email to a mail group of which I am a member.  The strange thing is that the email in my sent folders shows a good key signature with the exact Key fingerprint, but when I send an e-mail in reply to a cloud provider (where my team is contacted via a mail group) and the email shows back up in my inbox, the signature is showing invalid with the exact same Key fingerprint.  Both were sent via Kmail this morning using the exact same key.

First message in "Sent":
Message was signed by jappleii@redhat.com (Key ID: 0x928F06C71B1C271C).
The signature is valid and the key is fully trusted.

Second message in "Inbox":
Message was signed with unknown key 0x928F06C71B1C271C.
The validity of the signature cannot be verified.
Status: Bad signature

However, all of the signatures show clean in Thunderbird for both emails.
Comment 5 Bug Janitor Service 2022-12-17 05:13:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-01 05:20:22 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!