In de-vs compliance mode a DECRYPTION_COMPLIANCE_MODE status line should be emitted when compliant algos where used for encryption. However, if the data has also been encrypted with a password that status line is not emitted if OCB mode was used. The result is that for example kleopatra claims that the data was not compliant encrypted.
Description
Description
Revisions and Commits
Revisions and Commits
| rG GnuPG | |||
| rG9f30a5fd8cb7 gpg: Fix de-vs compliance with OCB and additional password. | |||
| rGd720c584f1f2 gpg: Make OCB mode compliant in de-vs mode. | |||
| rG6771ed4c1322 gpg: Fix de-vs compliance with OCB and additional password. | |||
| rGa73c88817ce2 gpg: Make OCB mode compliant in de-vs mode. | |||
Related Objects
Related Objects
Event Timeline
Comment Actions
In contrast to gnupg22 master did not proper show OCB compliance - not everything has yet been forward ported. But we can do so now and test master by setting GNUPG_ASSUME_COMPLIANCE=de-vs
Comment Actions
Tested with VS-Desktop-3.3.90.12-Beta
The DECRYPTION_COMPLIANCE_MODE status line is now emitted for an VS-NfD compliant encryption with OCB mode, too