summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib
diff options
context:
space:
mode:
authortb <>2023-10-09 16:03:57 +0000
committertb <>2023-10-09 16:03:57 +0000
commita9f7a1b523db0ec0d52c811aaf20f0c4cf7c9e33 (patch)
treeed572206365cdd923495da951c81dc4054218bbf /src/lib/libc/stdlib
parentb0458f52022f632ea4c4b230c7728c82285ac60c (diff)
downloadopenbsd-a9f7a1b523db0ec0d52c811aaf20f0c4cf7c9e33.tar.gz
openbsd-a9f7a1b523db0ec0d52c811aaf20f0c4cf7c9e33.tar.bz2
openbsd-a9f7a1b523db0ec0d52c811aaf20f0c4cf7c9e33.zip
Clarify documentation of X509_ALGOR_{set0,set_md}()
The X509_ALGOR_set0() and X509_ALGOR_set_md() documentation comes from upstream, which means it is as sloppy as the code and as vague as your average upstream manpage. Be precise on what X509_ALGOR_set0() does on different inputs and document return values and failure modes. X509_ALGOR_set_md() is a void function that calls X509_ALGOR_set0() in a way that can fail, leaving alg in a corrupted state. Document when that can occur and how to avoid or detect that, but do not go too far, because EVP_MD_meth_new(), one potential source of failures, is a whole another can of worms. joint work with schwarze
Diffstat (limited to 'src/lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions