| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
mark OBJ_create_and_add_object() as intentionally undocumented
|
|
|
|
|
| |
because OBJ_nid2obj(3) is already long and
more functions related to OBJ_create(3) have to be documented.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While it was probably a mistake that steve@ made some i2c_*() and c2i_*()
functions public back in 2000 and while we would like to delete them from
the API, it may not be possible to delete this particular function because
in contrast to the others (which are already marked as intentionally
undocumented), this one is used by various real-world software, so for now,
explain what it does, just in case people find it in existing code.
While here, use the familiar term "byte" that we generally use
throughout all our manual pages, even though the ASN.1 standard
uses the term "octet" instead, which is more precise only in theory.
|
| |
|
|
|
|
| |
that are intentionally undocumented
|
| |
|
| |
|
|
|
|
| |
using parts of the text from SMIME_read_CMS(3) and SMIME_read_PKCS7(3)
|
|
|
|
|
| |
certainly not perfect, but arguably better than the even terser
PEM_write_bio_CMS_stream(3) and PEM_write_bio_PKCS7_stream(3)
|
|
|
|
| |
still vague in various respects, but it's a start
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The API surrounding this is so complicated and streaming is so rarely
used in practice that describing this in more detail is not a priority
right now. The documentation of the wrapper BIO_new_CMS(3) is also
rather vague, and BIO_new_PKCS7() isn't described at all so far.
|
|
|
|
|
| |
mention which argument values can be used to not change the respective fields,
and tweak a few additional wordings
|
| |
|
| |
|
|
|
|
|
| |
B_ASN1_DIRECTORYSTRING, B_ASN1_PRINTABLE, B_ASN1_DISPLAYTEXT, B_ASN1_TIME,
DIRSTRING_TYPE, PKCS9STRING_TYPE
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Seeing the symbolic names in addition to the magic numbers
makes it esier to understand the text.
|
| |
|
|
|
|
|
|
| |
While here, tweak some wordings a bit to make it less likely that
readers confuse the type held by an ASN1_TYPE object with the type
of the ASN1_TYPE object itself, which is always V_ASN1_ANY.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
There is no need to explain well-known acronyms that are widely
used outside OpenSSL, too (like AES, ASN.1, CMS, ECDSA, PKCS...),
but OpenSSL uses plenty of idiosyncratic naming elements that
deserve to be explained (like d2i, ex, get0, ndef, sk, ...).
Requested by jsing@; feedback and OK tb@.
|
| |
|
|
|
|
| |
while here, improve some of the existing text in minor ways
|
|
|
|
| |
discussed with jsing@
|
|
|
|
| |
as intentionally undocumented; discussed with jsing@
|
|
|
|
|
|
| |
In order to not forget it, already remove the statements
that these APIs are currently implemented as macros:
Not saying that doesn't make the documentation wrong.
|
|
|
|
| |
ok schwarze
|
| |
|
|
|
|
|
|
|
|
|
| |
While here,
* call the function arguments "content_length" rather than just
"length" to make it less likely that the reader confuses them with
the total length returned by ASN1_object_size(3);
* state that only the short form is supported for content_length <= 127;
* add the missing STANDARDS section.
|
|
|
|
| |
as intentionally undocumented
|
| |
|
|
|
|
| |
ok schwarze@
|
|
|
|
| |
replace the BUGS section with a shorter CAVEATS section
|
|
|
|
|
|
|
|
|
|
|
| |
While here, also improve the rest of the page:
* add missing BIO_TYPE_* constants
* describe BIO_TYPE_START
* better function argument names
* more precision in the descriptions and regarding the RETURN VALUES
* lots of wording improvements
* improve the coding style below EXAMPLES
* delete a BUGS section describing cretaceous behaviour
|
|
|
|
|
|
| |
from <Malgorzata dot Olszowka at stunnel dot org>
via OpenSSL commit 256989ce in the OpenSSL 1.1.1 branch,
which is still under a free license
|
| |
|
| |
|
|
|
|
|
|
| |
not yet available.
ok schwarze
|
| |
|
|
|
|
| |
i2a_ASN1_ENUMERATED(3), and a2i_ASN1_ENUMERATED(3)
|
|
|
|
| |
thanks Matthias Schmidt
|
| |
|