diff options
author | tb <> | 2023-10-10 13:59:47 +0000 |
---|---|---|
committer | tb <> | 2023-10-10 13:59:47 +0000 |
commit | 5cbf5fcfb7c8f024018bdd341230dd05f331967a (patch) | |
tree | 839fb7d8c6ba2e45887042205322c320300755fc /src/lib/libc/stdlib/atexit.c | |
parent | d808914bdc17a47e22e7adf00aa95bf465f95b4f (diff) | |
download | openbsd-5cbf5fcfb7c8f024018bdd341230dd05f331967a.tar.gz openbsd-5cbf5fcfb7c8f024018bdd341230dd05f331967a.tar.bz2 openbsd-5cbf5fcfb7c8f024018bdd341230dd05f331967a.zip |
Improve X509_ALGOR_new(3) documentation
The previous wording was misleading since the result of X509_ALGOR_new()
is not actually an empty X509_ALGOR object. Rather, it contains the
undefined ASN1_OBJECT returned by OBJ_nid2obj(NID_undef). Therefore using
X509_ALGOR_get0(3) for error checking X509_ALGOR_set_md() is not trivial.
So: change the initial paragraph into a general intro referring to the
OpenSSL API needed to interface with X509_ALGOR and write a new paragraph
documenting X509_ALGOR_new(3) and drop the incorrect suggestion of an error
check. Notably there's now a reference to the OBJ_nid2obj() family without
which one cannot really use X509_ALGOR_* for anything at all.
With and ok schwarze
Diffstat (limited to 'src/lib/libc/stdlib/atexit.c')
0 files changed, 0 insertions, 0 deletions