| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
* add the missing STANDARDS sections
* mark up ASN.1 type names
* GOST does not need an ENGINE in LibreSSL, so don't use it as an example
* and minor wording improvements and typo fixes
|
|
|
|
|
|
| |
* mark up ASN.1 type and field names
* move the RFC reference to STANDARDS
* and minor wording improvements
|
|
|
|
|
|
|
|
|
|
| |
* do not jump back and forth among functions
* show data type - NID correspondance in a table
* make the difference between content type and embedded content clearer
* add the missing STANDARDS section
* mark up ASN.1 type names
* remove some text that says nothing
* and minor wording improvements
|
|
|
|
|
|
|
|
| |
* add the missing STANDARDS section
* more precision below RETURN VALUES
* simplify some overly verbose text
* mark up ASN.1 type names
* and minor wording improvements and typo fixes
|
|
|
|
|
|
|
|
| |
* add the missing STANDARDS section
* mark up ASN.1 type names
* avoid some repetitions
* make some lists more palatable in -column form
* and minor wording improvements and typo fixes
|
|
|
|
| |
and mention a trap set by EC_KEY_copy(3)
|
| |
|
|
|
|
| |
and EC_KEY_set_ex_data(3)
|
|
|
|
|
|
|
| |
* do not jump back and forth among different arguments and flags
* add the missing STANDARDS section
* mark up ASN.1 type names
* and several wording improvements
|
|
|
|
|
|
| |
* add the missing STANDARDS section
* mark up ASN.1 type names
* and minor wording improvements and typo fixes
|
|
|
|
|
|
| |
* add the missing STANDARDS section
* mark up ASN.1 type names
* and minor wording improvements
|
|
|
|
|
|
|
|
| |
* do not jump back and forth between different arguments
* display the flags in a proper list
* add the missing STANDARDS section
* mark up ASN.1 type names
* and minor wording improvements
|
|
|
|
|
| |
jsing@ provided crucial help regarding the content;
tweaks and OK tb@
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* avoid repetitions and jumping back and forth between the functions
* more precision regarding which ASN.1 types and fields are involved
* mark up the ASN.1 type and field names
* explain CMS_REUSE_DIGEST more precisely
* move the discussion of attributes to CMS_NOATTR where it belongs
* GOST does not need an ENGINE in LibreSSL, so don't use it as an example
* add the missing STANDARDS section
* and minor wording improvements
|
|
|
|
|
|
|
|
| |
* 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.
|