https://bugs.kde.org/show_bug.cgi?id=385687
--- Comment #6 from ekaratsio...@mtg.de --- Hi, report is on the way. About the anaylsis of the test cases I will revisit them and report in this ticket. As far as I remember revocation checking is a big issue, since the CRL is cached probably not using the CRL distribution points setting in the certificate (I believe so because each certificate has a distinct CRLDP). Therefore, if a CA produces certificates with different CRLDPs which point to CRLs with different content, the cached CRL is used for every certificate and checking revocation is not infeasible. This behaviour did not allow us to perform functional tests for example about the validity of a CRL, therefore we cannot do not know whether other issues concerning CRLs exist. Emptying the cache from within KMail/Kleopatra, which was the target application, did not produce the desired results. Best Regards Vangelis -- You are receiving this mail because: You are watching all bug changes.
