https://bugs.kde.org/show_bug.cgi?id=385687
Andre Heinecke <aheine...@intevation.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |UPSTREAM
--- Comment #3 from Andre Heinecke <aheine...@intevation.de> ---
I've now split this issue dump up into multiple issues assigned to their proper
components. I still only see one KMail issue here, which I moved out into a
standalone bug.
My evaluation is that CERT_PATH_COMMON_10 is the most serious issue as it might
result in a visible good signature for an expired certificate.
I'm resolving this as upstream because all issues are reported upstream or
moved into a standalone issue.
The split is:
For CERT_PATH_ALGO_STRENGTH_01 CERT_PATH_ALGO_STRENGTH_02
https://dev.gnupg.org/T3952
For CERT_PATH_COMMON_05 Bug 393675 But it might still turn out to be a GPGME
issue.
For CERT_PATH_COMMON_08 CERT_PATH_COMMON_10 https://dev.gnupg.org/T3953
For CERT_PATH_COMMON_13 https://dev.gnupg.org/T3954
For CERT_PATH_EMAIL_04 https://dev.gnupg.org/T3955
--
You are receiving this mail because:
You are watching all bug changes.
