As the RNG in GnuPG 2.3 is not compliant with de-vs nearly all operations in de-vs mode lead into "Forbidden" errors.
This should be caught early and handled with a warning message from Kleopatra to avoid strange situtations where nothing really works.
| rLIBKLEO Libkleo | |||
| rLIBKLEOa66a97a98331 Ignore compliance_de_vs for 2.2.28 to 2.2.33 | |||
| rLIBKLEOa556440db222 Make de-vs compliance checks more rigid | |||
| rLIBKLEOb13310007a17 Add the possibility to fake int crypto config entries in tests | |||
| rLIBKLEOd430be63ab30 Add new helpers for checking de-vs compliance of GnuPG | |||
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA96928c1e4501 Enable encrypt/sign button if GnuPG is compliant | |||
| rKLEOPATRAc770b6e52e58 Restrict the background color to the push button | |||
| rKLEOPATRA2238fed43a3d Inform user if signing/encrypting is not possible due to non-compliance | |||
| rKLEOPATRA879224193690 Show an error message when signing/encrypting with non-compliant GnuPG | |||
| rKLEOPATRAb823dc581954 Add a self-test checking de-vs compliance of GnuPG | |||
| rKLEOPATRA83dbedefc12b Show de-vs compliance in status bar if de-vs compliance is configured | |||
| rKLEOPATRAda7567ea797a Make de-vs compliance checks more rigid | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | • ebo | T5362 Kleopatra: Add warning in compliance mode if gnupg version is not compliant | ||
| Resolved | aheinecke | T5653 de-vs and GnuPG 2.3.3 error |
Result of self-test with failed compliance:
Sign/Encrypt files dialog with error message and disabled Encrypt button:
Notepad with warning and disabled Sign / Encrypt button:
Decryption and normal verification of signatures is still possible (unless GnuPG complains because of enforced de-vs compliance).