Page MenuHome GnuPG

Kleopatra: Improve handling of MDC errors
Closed, ResolvedPublic


This should have probably been done for the 3.1.2 release. So I give it high priority as it should definitely done before the next release.

We are starting to get reports by users that files fail to decrypt with Gpg4win 3.1.2 and they only see the generic "Decryption Failed" error. (e.g. )

I think the problem is in GPGME actually. (Also see T3714 ) As the decryption result should provide the correct error. But we might also use the new flag for legacy no mdc to improve the handling in Kleopatra.



Revisions and Commits

Event Timeline

We have two cases:

  1. No MDC with a "modern" cipher algo

In that case we don't get any status from GnuPG except "Decryption Failed"

  1. No MDC with an "old" cipher algo

This is already handled and provided by gpgme++ with legacyCipherNoMDC

Both cases currently look like this:

Which is very bad as it gives users no indication what went wrong.

aheinecke changed the task status from Open to Testing.Jul 4 2018, 12:31 PM

Now we have this:

Gpg4win-3.1.3 was released.

I'm new here, therefore I'm unsure whether this posting is correct at this position.
Within my organisation we have ongoing troubles with the error described here, with windows version 3.1.3 there is no such button "force decryption" as documented here.

Can you help? Regards Karl