| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
* 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@
|
|
|
|
| |
missed during code scan.
|
|
|
|
| |
OK claudio@
|
| |
|
|
|
|
|
|
|
| |
current ber element.
OK claudio@
Seems sensible to deraadt@
|
|
|
|
|
|
|
|
| |
Right now all consumers use 'e' at the end of the list, so no regressions
should be introduced.
OK claudio@
Seems sensible to deraadt@
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
| |
ok yasuoka@
|
|
|
|
|
|
|
|
|
| |
where ber is utilized. This also allows us to remove the ber->be_next
check, which can cause weird behaviour, because a NULL be_next would result
in parsing the last element twice.
OK claudio@ on previous version
OK rob@
|
|
|
|
|
|
|
|
| |
* 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 seems that the CMS code is currently the only code in existence that
uses this function.
|
| |
|
|
|
|
| |
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
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
|
|
|
| |
does exist -- execv(3). Still call this a family but without "Nm".
Adjust Xr in various pages to refer to the precise function used
rather than the family, in most cases the semantics of execve(2) are
being referenced, so change the Xr.
ok jmc
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This also removes return checks since arc4random_buf() does not fail.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
(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.
|
| |
|
| |
|
|
|
|
| |
Files are identical once whitespace and newlines are removed.
|