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)
Showing
- Configure 21 additions, 2 deletionsConfigure
- crypto/err/err_all.c 1 addition, 1 deletioncrypto/err/err_all.c
- include/openssl/crmf.h 2 additions, 2 deletionsinclude/openssl/crmf.h
- include/openssl/crmferr.h 1 addition, 1 deletioninclude/openssl/crmferr.h
- util/libcrypto.num 74 additions, 74 deletionsutil/libcrypto.num
- util/mkerr.pl 1 addition, 1 deletionutil/mkerr.pl
Please register or sign in to comment