Document EVP_PKEY_new_CMAC_key(3) in sufficient detail such that readers

stand a chance of using the API correctly.

Admittedly, having so much text below EXAMPLES is somewhat unusual.
While all that information is required to use the function correctly,
strictly speaking, it is not part of the specification of what
EVP_PKEY_new_CMAC_key(3) does, so it woundn't really belong
in the DESCRIPTION.

Now, designing an API function in such a way that using it correctly
requires lots of information about *other* functions and such that
all that additional information does not belong into the manual pages
of those other functions (both because that would cause distractions
in various other manual pages and because it would scatter required
information around lots of different pages) is certainly not stellar
API design.  But we can't help that because these APIs were all
originally designed by OpenSSL.

Significant feedback and OK tb@.

0 files changed, 0 insertions, 0 deletions