openbsd/src/regress/lib/libcrypto/man, branch OPENBSD_7_1_BASE

support processing

2021-12-18T19:55:26+00:00

To ease maintenance, structure the lists of intentionally undocumented

2021-12-16T12:26:40+00:00

symbols according to the reason (internal, obsolete, postponed) and according to the header file (asn1, objects, x509, ...). Also, add some minor tweaks needed for .

Some more ASN.1 struct types that are postponed (because they are

2021-12-15T16:36:39+00:00

related to templating macros) or intentionally undocumented. Apart from NETSCAPE, PCTX, and low-level templating stuff, all ASN.1 functions, types, and macros are now documented.

be more specific which NETSCAPE stuff to ignore, and why

2021-12-07T17:01:08+00:00

Some improvements allowing to handle asn1.h and x509v3.h:

2021-12-07T16:43:24+00:00

* handle multiple qualifiers on the function return type * handle function pointer type declarations * handle unions inside structs * handle forward struct declarations * handle "typedef const" * handle ASN1_F_, ASN1_R_, and X509V3_R_ error constants * handle "#if defined" in the same way as "#ifdef" * skip whitespace between "#" and "define" * skip whitespace before C comments * ignore TYPEDEF_D2I2D_OF

Mark the X509_VERIFY_PARAM_ID variable type as intentionally

2021-11-19T17:42:22+00:00

undocumented. It is an opaque struct used only internally, as a sub-object of the public X509_VERIFY_PARAM type. All related API functions take X509_VERIFY_PARAM arguments, so X509_VERIFY_PARAM_ID is of no interest to the user.

Make function prototype parsing a bit stricter,

2021-11-19T17:29:17+00:00

reducing the risk of accidental misparsing: Require whitespace after the function return type (before the asterisk indicating that the function returns a pointer, if any) and do not accept whitespace between the function name and the opening parenthesis of the parameter list. These changes are not a problem because we want that style for KNF reasons anyway.

Very quick and dirty script to help me check that the symbols

2021-11-19T09:15:35+00:00

in one of the public openssl/ header files are all documented. Before attempting to read this code, make sure that you are fully vaccinated against leaning toothpick syndrome. Example usage: ./check_complete.pl x509_vfy ./check_complete.pl -v x509 | less Intentionally not linked to the build. jsing@ agrees with the general direction.