| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
* state the common, general purpose up front
* more precision regarding which ASN.1 types and fields are involved
* mark up the ASN.1 type and field names
* add the missing STANDARDS section
* and minor wording improvements
|
|
|
|
|
|
|
| |
* add missing STANDARDS section
* avoid repetitions and jumping back and forth among functions
* describe the difference between 0 and 1 more precisely and more concisely
* mark up the ASN.1 type and field names
|
|
|
|
| |
it looks like this was the last bad .Xr in *CMS*(3)
|
| |
|
|
|
|
|
|
| |
names and documenting these two functions, CMS_decrypt_set1_pkey(3)
and CMS_decrypt_set1_key(3) right here in this same page.
While here, simplify and improve some wording.
|
|
|
|
| |
actually documented, so write the documentation from scratch.
|
|
|
|
|
|
|
|
|
|
| |
which is still under a free license:
* mention pem_password_cb in NAME and SYNOPSIS
* recommend -1 as pem_password_cb error return for OpenSSL compat
* minor improvements to the pass_cb() example code
* mention that the pass phrase is just a byte sequence
* and minor wording and markup improvements
|
| |
|
|
|
|
|
|
|
| |
(which are still under a free license) with pod2mdoc(1) now that
jsing@ has begun work to provide these APIs.
Some formatting was improved and some typos were fixed, but apart
from that, little was changed, so there is still much to polish.
|
| |
|
|
|
|
|
| |
but failed to provide any real information.
OK tb@ jmc@
|
|
|
|
|
|
|
|
|
| |
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@.
|
|
|
|
| |
references were already given below RETURN VALUES right above
|
|
|
|
|
| |
and to isolated obsolete pages;
OK bcook@ jmc@
|
|
|
|
|
|
|
|
|
|
| |
which is now supposed to be opaque.
OK tb@
I checked that all the information contained in comments in the
display is available from the appropriate places in RSA_meth_new(3)
and RSA_set_flags(3). Note that the comments regarding "mod_exp",
"init", and "finish" were half-misleading simplifications, anyway.
|
|
|
|
|
| |
Update the documentation.
OK tb@ jmc@
|
|
|
|
| |
OK tb@ jmc@
|
|
|
|
|
|
| |
These references were misleading because these functions are no
longer used internally and applications should not call them either.
Issue brought up by tb@.
|
| |
|
| |
|
|
|
|
|
|
|
| |
PKCS5_PBKDF2_HMAC(3) to the top level page evp(3). The leaf pages
still have backlinks to the group entry page EVP_DigestInit(3),
which is enough.
Redundancy and asymmetry pointed out by tb@.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
| |
|
|
|
|
| |
for consistency with all the other X509_STORE_*(3) manual pages
|
|
|
|
|
| |
and add a sentence pointing to the detailed description
in RSA_get_ex_new_index(3), worded like in DH_get_ex_new_index(3).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
still under a free license, tweaked by me
|
| |
|
|
|
|
|
|
| |
The algorithm is insecure and yet its description would spread over
three paragraphs in the cipher list, including remarkable advice
like using a 40 bit key length.
|
|
|
|
|
| |
this moves a large number of functions out of the way that are no
longer the latest and greatest. Also mention a few that were missing.
|
|
|
|
| |
that are also documented in OpenSSL 1.1.1 (still under a free license)
|
|
|
|
| |
in r1.28 when the AES ciphers were split into their own manual.
|
|
|
|
| |
patch from Peter Piwowarski <peterjpiwowarski at gmail dot com>
|
|
|
|
|
|
|
| |
AES wrap modes, the function EVP_CIPHER_CTX_set_flags(3) needed to
set it, and the companion functions EVP_CIPHER_CTX_clear_flags(3)
and EVP_CIPHER_CTX_test_flags(3).
With help and an OK from tb@.
|
|
|
|
|
| |
from Jan Stary <hans at stare dot cz>.
Where here, correct one .Vt NULL -> .Dv NULL.
|
|
|
|
|
|
|
|
|
|
|
|
| |
both resulting pages are still long.
Mention a number of missing functions.
Add some text from the OpenSSL 1.1.1 EVP_aes.pod manual page,
which is still under a free license.
Add missing HISTORY information.
Triggered by tb@ providing EVP_aes_{128,192,256}_wrap(3)
in evp.h rev. 1.74.
|
| |
|
|
|
|
|
|
|
|
|
| |
Document it.
Even though OpenSSL muddles the waters by lumping the description
together with the other EVP_PKEY_get0_*() functions, describe it
separately because a char * has no reference count and because
the function fills in an additional length parameter.
|
|
|
|
|
|
| |
From Viktor Dukhovni via OpenSSL commit 0df65d82 Jun 12 11:51:53 2018 -0400
which is still under a free license because it is before the 1.1.1 branch point.
While here, add several missing const qualifiers.
|
|
|
|
| |
so mention it here, too.
|
|
|
|
|
|
| |
From David dot von dot Oheimb at siemens dot com
via OpenSSL commit b8c32081 Feb 10 15:45:11 2018 +0100, which is still
under a free license because it is before the 1.1.1 branch point.
|
| |
|
|
|
|
|
|
|
| |
because CRYPTO_set_locking_callback() is now a no-op
and was never documented in the first place;
no text change;
requested by jmc@ long ago
|
|
|
|
|
|
|
| |
and that don't do anything in OpenSSL either;
no significant amount of text remains from OpenSSL, so change the
Copyright information and license of CRYPTO_set_locking_callback.3;
OK inoguchi@ jmc@
|