summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/BIO_f_base64.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* spellingjsg2023-09-111-3/+3
|
* Mark EVP_ENCODE_LENGTH() and EVP_DECODE_LENGTH() as intentionallyschwarze2023-09-101-2/+6
| | | | | | | undocumented because they do not describe properties of the Base64 encoding but add arbitrary constant lengths, hence being implementation details of BIO_f_base64(3). Besides, they are practically unused outside evp/bio_b64.c.
* Document the RETURN VALUES of BIO_method_type(3) and BIO_method_name(3)schwarze2023-04-111-2/+11
| | | | for the various BIO types.
* Fix example stringtb2022-12-071-4/+4
| | | | | | If you want to Base64-encode "Hello World\n" using a BIO, you had better pass "Hello World\n" into it, not something slightly different... While we're touching this, we might as well write it the way K&R did...
* Tree structure for manual pages: crypto(3) links to 33 functionschwarze2019-06-061-3/+4
| | | | | | | | | | | group pages, and these link on to all their second-level subpages. Only a handful of second-level pages have third-level subpages. So all crypto pages can now be reached from the www.libressl.org frontpage via at most four clicks, in most cases three clicks. Also link back from leaf pages to their respective group pages and add a couple of additional links between related pages. Triggered by a question from deraadt@. OK jmc@ tb@
* In evp.h rev. 1.59 2018/05/02 15:51:41, tb@ added a const qualifierschwarze2018-05-021-3/+3
| | | | | to the return value of BIO_f_base64(3), BIO_f_cipher(3), and BIO_f_base64(3). Update the documentation.
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-271-3/+3
| | | | on the web, so fix up SSLeay HISTORY accordingly
* evp.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-201-2/+6
|
* Delete a cross reference to the non-existent manual page BIO_set_flags(3),schwarze2017-01-061-11/+8
| | | | | | | | | | | | | reported by jmc@. Documenting that function would be a bad idea. All other flags are used internally and should better not be tampered with. It looks like an internal function that was made public by mistake, then abused for an unrelated user interface purpose: a classic case of botched user interface design. Instead, only show how to use this function for this one specific purpose. While here, delete a sentence from the DESCRIPTION that merely duplicated content from the BUGS section.
* make sure that all the BIO pages point back to the master page BIO_new(3)schwarze2016-12-061-2/+4
|
* add copyright and licenseschwarze2016-11-111-3/+52
| | | | | and change the reference to BIO_set_flags() from .Fn to .Xr: we do have that function and we should import the manual
* various cleanup;jmc2016-11-071-7/+7
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* Add missing CVS Mdocdate tags. No text change, except for the changeschwarze2015-09-091-1/+1
| | | | of date that can't be helped.
* second batch of perlpod(1) to mdoc(7) conversionschwarze2015-02-141-0/+80