Richard Levitte 538f38db50 Clear CRMF vs CMP confusion ... In the development of the CRMF sub-system, there seems to have been some confusion as to what configuration option should be used. 'no-crmf' was added, but the C macro guards were using OPENSSL_NO_CMP rather than OPENSSL_NO_CRMF... In fact, we want 'no-cmp', but since the CRMF code is part of CMP, we need 'no-crmf' to depend on 'no-cmp'. We do this by making 'crmf' a silent "option" that get affected by 'cmp' by way of %disable_cascades. This allows options to be "aliases" for a set of other ones, silent or not. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/8897)		2019-05-20 16:19:00 +02:00
..
internal	EVP_FETCH: deal with names without pre-defined NIDs	2019-05-12 13:43:38 -07:00
openssl	Clear CRMF vs CMP confusion	2019-05-20 16:19:00 +02:00