| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
for the various BIO types.
|
|
|
|
|
|
| |
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...
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
| |
to the return value of BIO_f_base64(3), BIO_f_cipher(3), and
BIO_f_base64(3). Update the documentation.
|
|
|
|
| |
on the web, so fix up SSLeay HISTORY accordingly
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
and change the reference to BIO_set_flags() from .Fn to .Xr:
we do have that function and we should import the manual
|
| |
|
| |
|
|
|
|
| |
of date that can't be helped.
|
|
|