| Summary: | SMIME/X509: Encrypted message Not enough information to check signature. %1(I18N_ARGUMENT_MISSING) | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Achim Bohnet <ach> |
| Component: | UI | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | dennis.schridde |
| Priority: | NOR | ||
| Version: | 5.4.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
mail signed with my key. (With 'MPG CA' as 3rd level CA)
kwatchgnupg log of mail from attachemnt above ( differs starting at line 73 from (3) ) watchgnupg log of a mail with a successully verified signature (with different 3rd level CA than 'MPG CA') Screenshot of kleopatra with 'non uniq' cert 'MPG CA' |
||
|
Description
Achim Bohnet
2017-03-31 15:27:47 UTC
Git commit 2e6ad643072a5de40b96365d352966244f1c0116 by Montel Laurent. Committed on 03/04/2017 at 11:33. Pushed by mlaurent into branch 'Applications/17.04'. Fix i18n(...) it's a "block" variable here. M +2 -2 messageviewer/src/messagepartthemes/default/templates/signedmessagepart.html https://commits.kde.org/messagelib/2e6ad643072a5de40b96365d352966244f1c0116 Signing and encryption problem is described in https://bugs.kde.org/show_bug.cgi?id=378745 Maybe info there helps to unterstand the 'Signature verfication' fails. Created attachment 105035 [details]
mail signed with my key. (With 'MPG CA' as 3rd level CA)
Created attachment 105036 [details]
kwatchgnupg log of mail from attachemnt above ( differs starting at line 73 from (3) )
Created attachment 105037 [details]
watchgnupg log of a mail with a successully verified signature (with different 3rd level CA than 'MPG CA')
Apple Mail marks signed mail from our coorporate members, with 'MPG CA' in chain as okay. Nobody complains on the our List about broken signartues. (I bet all OS & MTA Agents combinations are used to read those mails) Look like kmail fails to update the CRL of 'MPG CA'. Maybe that's the signature check failure reason? At least I've found other signed mail with same 1st&2nd level CAs but different 3rd level CA, that is successfully verified. Attachments: 1) s_mine_signed.mbox: mail signed with my key. (With 'MPG CA' as 3rd level CA) 2) smime-bad-sig-check.log: kwatchgnupg log of mail from attachemnt above ( differs starting at line 73 from (3) ) 3) smime-good-sig-check.log: watchgnupg log of a mail with a successully verified signature (with different 3rd level CA than 'MPG CA') Hope this helps! Achim Created attachment 105038 [details]
Screenshot of kleopatra with 'non uniq' cert 'MPG CA'
About the 'mehrdeutiger Name' (en: not unique name) error in the log when trying to update the CRL: I see in kleopatra that there are 2 'MPG CA' keys. Details see attached screen shot.
When I enable S/MIME OCSP checks, I also see the following in the logs: ``` ... 4 - 2017-05-19 17:21:21 gpgsm[8356]: DBG: chan_10 -> ISVALID <<REDACTED>> 4 - 2017-05-19 17:21:21 gpgsm[8356]: DBG: chan_10 <- ERR 167772220 Not supported <Dirmngr> ... 4 - 2017-05-19 17:21:36 gpgsm[8562]: DBG: chan_10 -> ISVALID <<REDACTED>> 4 - 2017-05-19 17:21:36 gpgsm[8562]: DBG: chan_10 <- ERR 167772220 Not supported <Dirmngr> 4 - 2017-05-19 17:21:36 gpgsm[8562]: certificate <<REDACTED>> 4 - 2017-05-19 17:21:36 gpgsm[8562]: checking the CRL failed: Not supported 4 - 2017-05-19 17:21:36 gpgsm[8562]: validation model used: shell ... ``` When I disable CRL checks, I can send S/MIME encrypted & signed emails. 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! 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! 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! |