summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/ERR_load_crypto_strings.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove GOST documentationtb2024-03-051-3/+2
|
* Stop mentioning some ERR_load_*_strings that will be removedtb2023-07-211-6/+2
|
* Explicitly list all public functions in roff(7) commentsschwarze2021-11-111-6/+33
| | | | | that are related to this page but intentionally undocumented, to better support grepping the source directory for function names.
* minor polishing:schwarze2020-06-041-4/+10
| | | | | | * below SEE ALSO, point to the most similar function that is not deprecated * add a comment saying why ERR_load_ERR_strings() is intentionally undocumented * update the comment specifying the merge status
* Further improve the documentation of library initialization and configuration.schwarze2019-06-141-23/+6
| | | | | | | | | Among other improvements: * Use a uniform wording at the top of the DECSRIPTION for obsolete pages. * Better explain how to use a non-standard configuration file. * Remove obsolete functions from SEE ALSO. Triggered by some suggestions from tb@. Tweaks and OK tb@.
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-271-6/+9
| | | | on the web, so fix up SSLeay HISTORY accordingly
* bn.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-201-5/+7
|
* Document ERR_load_BN_strings(3).schwarze2017-01-261-11/+47
| | | | | | | | | | | | | | | | | jsing@ confirmed that this function is public and worth documenting. This page needs much more work, it is outrageously incomplete and unclear. For example, it remains unexplained what error strings are, what "registering" means and what the benefit for the application is, what happens if it is not done, or what happens if an error occurs after calling ERR_free_strings(3). I tried to read the code, but it is so contorted that i postponed that work. For example, it looks like there are hooks for applications to replace the functions used for registering strings by other, application-supplied functions, and, of course, there are many levels of macro and function wrappers. For now, i only documented the most obvious BUGS.
* Copyright and licenseschwarze2016-11-231-2/+50
|
* various cleanup;jmc2016-11-171-3/+3
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* convert ERR manuals from pod to mdoc; while reading this,schwarze2016-11-021-0/+48
i wtfed, laughed, puked, and cried in more or less that order...