Maniphest T6174

Option --require-comliance does not work in sign+encrypt mode
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• werner
	Aug 30 2022, 6:53 PM

Tags

Subscribers

Description

In de-vs mode the new --require-compliance option does not have an effect when doing sign+encrypt with an non-compliant key. Test can easily be done by encrypting to an cv25519.

Details

Version: <= 2.2.37

Revisions and Commits

rG GnuPG
	rG46f9b0071f54 gpg: Fix assertion failure due to errors in encrypt_filter.
	rGa51067a21f68 gpg: Make --require-compliance work for -se
	rGaa0c942521d8 gpg: Fix assertion failure due to errors in encrypt_filter.
	rGf88cb12f8e3c gpg: Make --require-compliance work for -se

Related Objects

Mentioned In: T6159: Release GnuPG 2.2.38

Event Timeline

• werner triaged this task as High priority.Aug 30 2022, 6:53 PM

• werner created this task.

• werner created this object with edit policy "Contributor (Project)".

• werner added a commit: rGf88cb12f8e3c: gpg: Make --require-compliance work for -se.Aug 31 2022, 1:59 PM

• werner added a commit: rGaa0c942521d8: gpg: Fix assertion failure due to errors in encrypt_filter..

• werner closed this task as Resolved.Aug 31 2022, 5:46 PM

• werner mentioned this in T6159: Release GnuPG 2.2.38.Aug 31 2022, 6:31 PM

• werner added a commit: rGa51067a21f68: gpg: Make --require-compliance work for -se.Sep 29 2022, 3:17 PM

• werner added a commit: rG46f9b0071f54: gpg: Fix assertion failure due to errors in encrypt_filter..

• ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jul 24 2023, 2:12 PM