Bug 291151

Summary:	More user friendly error messages (SMIME)
Product:	[Applications] kmail2	Reporter:	karaluh <karaluh>
Component:	crypto	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kdenis, montel, sknauss
Priority:	NOR	Keywords:	triaged
Version:	1.99.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description karaluh 2012-01-10 10:43:09 UTC

Version:           1.99.0 (using KDE 4.7.4) 
OS:                Linux

Signature in my bank's e-mails according to kmail aren't signed properly, I don't know what the problem is however. Audit log tells me a lot, but I don't understand anything from it. Kmail should clearly state what the problem is and hopefully how to fix it. 


Reproducible: Always

Steps to Reproduce:
.


Expected Results:  
.

OS: Linux (i686) release 3.0.0-15-generic
Compiler: gcc

Comment 1 Laurent Montel 2012-11-06 17:41:56 UTC

Which error do you have ? how to reproduce it ? etc.

Comment 2 karaluh 2012-11-07 10:41:25 UTC

(In reply to comment #1)
> Which error do you have ? how to reproduce it ? etc.

I have an e-mail from my bank. It is signed, however kmail tels me, that there is not enough information to check the signature. When I choose to see the details, I'm informed, that there is not enough information to check the signature 0x585088937F4D71D9, and that the status is "no information about the status". When I see the audit log, I get this:



*
Weryfikacja danych zakończona

Tak

*  
Dane dostępne

Tak

*  
Podpis dostępny

Tak

*  
Analiza danych zakończona

Tak

*     
(algorytm skrótu danych: SHA1)



*  
Podpis 0

Zły

*     
(#0C000F5A225664567CAD2DAE326463C0/OU=VeriSign Class 2 OnSite Individual CA,O=VeriSign)



*     
(algorytm skrótu danych: SHA1)



*     
(algorytm skrótu atrybutów: SHA1)



*    
Łańcuch certyfikatów dostępny

Tak

*       
(brak certyfikatu głównego)



*       
(#0C000F5A225664567CAD2DAE326463C0/OU=VeriSign Class 2 OnSite Individual CA,O=VeriSign)



*         
(/1.2.840.113549.1.9.1=#696E74656C69676F40696E74656C69676F2E706C,CN=PKO Bank Polski SA CBE INTELIGO,OU=www.verisign.com/repository/CPS Incorp. by Ref.\,LIAB.LTD(c)99,OU=Security Department,O=Inteligo Financial Services,L=Warszawa,ST=Mazowieckie,C=PL)



*    
Łańcuch certyfikatów poprawny

Nie

*       
(Brak dirmngr)



*    
weryfikacja CRL/OCSP certyfikatów

Brak dirmngr

*  
Dołączone certyfikaty

3

*     
(#43DE45067E91ED3BB670E417526649B5/OU=VeriSign Trust Network,OU=(c) 1998 VeriSign\, Inc. - For authorized use only,OU=Class 2 Public Primary Certification Authority - G2,O=VeriSign\, Inc.,C=US)



*       
(/OU=VeriSign Class 2 OnSite Individual CA,O=VeriSign)



*     
(#0C000F5A225664567CAD2DAE326463C0/OU=VeriSign Class 2 OnSite Individual CA,O=VeriSign)



*       
(/1.2.840.113549.1.9.1=#696E74656C69676F40696E74656C69676F2E706C,CN=PKO Bank Polski SA CBE INTELIGO,OU=www.verisign.com/repository/CPS Incorp. by Ref.\,LIAB.LTD(c)99,OU=Security Department,O=Inteligo Financial Services,L=Warszawa,ST=Mazowieckie,C=PL)



*     
(#0C000F5A225664567CAD2DAE326463C0/OU=VeriSign Class 2 OnSite Individual CA,O=VeriSign)



*       
(/1.2.840.113549.1.9.1=#696E74656C69676F40696E74656C69676F2E706C,CN=PKO Bank Polski SA CBE INTELIGO,OU=www.verisign.com/repository/CPS Incorp. by Ref.\,LIAB.LTD(c)99,OU=Security Department,O=Inteligo Financial Services,L=Warszawa,ST=Mazowieckie,C=PL)



*
Dirmngr sprawny

Nie

*   
(Wywołanie connect dla IPC nie powiodło się)




Brak pomocy dla ,,gnupg.dirmngr-problem''. 
Brak pomocy dla ,,gpgsm.crl-problem''.

Comment 3 Sandro Knauß 2014-12-13 00:33:02 UTC

Sorry I do not understand pl - please translate it to english. (via setting->language, restart kmail afterwards) .

Comment 4 Denis Kurz 2016-09-24 17:58:06 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Sandro Knauß 2016-09-26 12:02:36 UTC

It is still an issue.

But onfortunatelly I don't have the knowlege, who do verify a correct SMIME signature.

Comment 6 Denis Kurz 2017-01-14 13:56:56 UTC

Sandro (or anyone else), which recent version did you experience this with? This bug is still set to version 1.99.0.

Comment 7 Andrew Crouthamel 2018-09-26 22:12:47 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 set the bug status 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 8 Andrew Crouthamel 2018-10-27 02:46:52 UTC

Dear Bug Submitter,

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!