Remove incorrect function counts

Vincent Lee spotted that I failed to update numbers that count how many
functions are documented here when removing {CRYPTO,OPENSSL}_realloc.
This isn't helpful info

Remove incorrect function counts

Vincent Lee spotted that I failed to update numbers that count how many
functions are documented here when removing {CRYPTO,OPENSSL}_realloc.
This isn't helpful information and nobody will remember to go look for
such numbers next time this page is adjusted, so remove the counts.

agreement from jmc

show more ...

Remove OPENSSL/CRYPTO_realloc documentation

Mention which functions are implemented as macros in the few cases
where that information was missing.

Document that OPENSSL_free() is required in some circumstances

BoringSSL uses the common trick of storing malloc metadata in a prefix
and then returning a pointer with an offset. Therefore callers m

Document that OPENSSL_free() is required in some circumstances

BoringSSL uses the common trick of storing malloc metadata in a prefix
and then returning a pointer with an offset. Therefore callers must not
call free() but OPENSSL_free().

Reported by dropk1ck via tobhe

ok beck jsing

show more ...

add links back to crypto(3) to function group entry pages
and to isolated obsolete pages;
OK bcook@ jmc@

found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballs
on the web, so fix up SSLeay HISTORY accordingly

crypto HISTORY up to 0.9.8zh; researched from OpenSSL git

crypto HISTORY up to 0.9.6; researched from OpenSSL git

crypto.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL git

tweak previous;

seperate these descriptions into seperate files to reduce confusion.
discussed with jsing
ok schwarze

minor cleanup;

Document and discourage those wrappers that we have and that OpenSSL
documents, too. There are many additional undocumented ones in our
public OpenSSL headers, but advertising those would be a bad i

Document and discourage those wrappers that we have and that OpenSSL
documents, too. There are many additional undocumented ones in our
public OpenSSL headers, but advertising those would be a bad idea.

Nothing of the text from OPENSSL_malloc.pod remains, so use my own
Copyright and license.

show more ...