| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
As far as LibreSSL is concerned, this terrible API is pushing up the
daisies.
|
| | |
|
| |
|
|
|
| |
The old description was vague, but strictly speaking a lie, so make it
more precise and turn the lie into a truth.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous wording was misleading since the result of X509_ALGOR_new()
is not actually an empty X509_ALGOR object. Rather, it contains the
undefined ASN1_OBJECT returned by OBJ_nid2obj(NID_undef). Therefore using
X509_ALGOR_get0(3) for error checking X509_ALGOR_set_md() is not trivial.
So: change the initial paragraph into a general intro referring to the
OpenSSL API needed to interface with X509_ALGOR and write a new paragraph
documenting X509_ALGOR_new(3) and drop the incorrect suggestion of an error
check. Notably there's now a reference to the OBJ_nid2obj() family without
which one cannot really use X509_ALGOR_* for anything at all.
With and ok schwarze
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The X509_ALGOR_set0() and X509_ALGOR_set_md() documentation comes from
upstream, which means it is as sloppy as the code and as vague as your
average upstream manpage. Be precise on what X509_ALGOR_set0() does on
different inputs and document return values and failure modes.
X509_ALGOR_set_md() is a void function that calls X509_ALGOR_set0() in a
way that can fail, leaving alg in a corrupted state. Document when that
can occur and how to avoid or detect that, but do not go too far, because
EVP_MD_meth_new(), one potential source of failures, is a whole another
can of worms.
joint work with schwarze
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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 some function arguments. Update the documentation.
|
| |
|
|
| |
on the web, so fix up SSLeay HISTORY accordingly
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
X509_REQ_get_signature_nid(3), in rev. 1.36 2018/02/22 16:58:45
X509_CRL_get_signature_nid(3), and in rev. 1.40 2018/02/22 17:09:28
X509_get0_tbs_sigalg(3). Merge the documentation from OpenSSL.
|
| |
|
|
| |
related to X.509 with .Vt such that they can be searched for.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod.
Explain what an X509_ALGOR object represents and where it is used.
Explain how copying works, like in similar pages.
New RETURN VALUES, SEE ALSO, and STANDARDS sections.
Some macro and wording fixes.
|
| | |
|
| |
|
