summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* fix typo, from OpenSSLschwarze2016-12-191-4/+4
| | | | | | commit 0b742f93ea7882a447f6523ac56a6f847d9f8e92 Author: Finn Hakansson <finn_hakansson@yahoo.com> Date: Thu Dec 15 12:58:19 2016 -0500
* Define X25519_KEY_LENGTH and use it so we have fewer magic numbers.jsing2016-12-172-6/+12
| | | | ok beck@
* Write new X509_ATTRIBUTE(3) manual page from scratch.schwarze2016-12-172-1/+101
| | | | | | | | | | Both functions are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file. The design and use of this data type feels horrific. If you understand PKCS#8 or PKCS#10 and can explain why this was designed as it is, your contribution to this manual page is welcome.
* Write a new manual page X509_REQ_new(3) from scratch.schwarze2016-12-172-1/+84
| | | | | | These four functions are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Document X509_REVOKED_new(3) and X509_REVOKED_free(3) and moveschwarze2016-12-163-49/+157
| | | | | | X509_REVOKED_set_serialNumber(3) and X509_REVOKED_set_revocationDate(3) into this new page. Replace irrelevant cross references with relevant cross references to X509_CRL* pages.
* Write X509_CRL_new(3) manual page from scratch. These four functionsschwarze2016-12-162-1/+92
| | | | | | | are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Link to all pages dealing with X509_CRL objects.
* Write new X509_CINF_new(3) manual page from scratch. These functionsschwarze2016-12-162-1/+99
| | | | | are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* Document ERR_FATAL_ERROR(3), tweaked by me.schwarze2016-12-161-7/+18
| | | | | | OpenSSL commit 036ba500f7886ca2e7231549fa574ec2cdd45cef Author: Benjamin Kaduk <bkaduk@akamai.com> Date: Thu Dec 8 12:01:31 2016 -0600
* Fix error in the description of BUF_reverse(3), tweaked by me.schwarze2016-12-161-5/+10
| | | | | | OpenSSL commit 498180de5c766f68f6d2b65454357bc263773c66 Author: Dmitry Belyavskiy <beldmit@gmail.com> Date: Mon Dec 12 15:35:09 2016 +0300
* markup fix;jmc2016-12-151-2/+2
|
* Add a STANDARDS section and mention the relevant section of the standard.schwarze2016-12-151-18/+9
| | | | | | | Link to X509_ALGOR_new(3) because one of the functions uses X509_ALGOR. Delete a sentence about a function we don't have. Delete another sentence that says nothing new. Remove some macros that we don't normally use.
* link back to X509_ALGOR_new(3)schwarze2016-12-151-3/+4
|
* Document X509_ALGOR_new(3) and X509_ALGOR_free(3)schwarze2016-12-151-17/+81
| | | | | | | | | 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.
* provide missing section number to Xr;jmc2016-12-151-2/+2
|
* Make sure all pages talking about X509_EXTENSION objectsschwarze2016-12-154-20/+22
| | | | link back to X509_EXTENSION_new(3).
* cut back some excessive cross referencesschwarze2016-12-151-9/+4
| | | | and link to X509_EXTENSION_new(3) instead
* Document X509_EXTENSION_new(3) and X509_EXTENSION_free(3) listedschwarze2016-12-151-53/+106
| | | | | | | | | in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Explain what an X509_EXTENSION object is and where it is used. Add STANDARDS references. Sort the functions into a more logical order. Link to all other pages dealing with X509_EXTENSION objects.
* Add a helper script, format-pem.pl: a filter to sort and pretty-printsthen2016-12-151-0/+107
| | | | cert.pem entries. ok jsg
* remove "(DEPRECATED)" from the Nd: none of the other base pagesjmc2016-12-151-3/+3
| | | | | | | document things this way and DESCRIPTION is clear anyway that this should not be used; wording of the Nd suggested by schwarze ok schwarze
* an Xr and new line fix;jmc2016-12-142-6/+6
|
* Document X509_NAME_dup(3) and X509_NAME_ENTRY_dup(3) listed inschwarze2016-12-141-2/+84
| | | | | | OpenSSL doc/man3/X509_dup.pod and d2i_X509_NAME_ENTRY(3) and i2d_X509_NAME_ENTRY(3) listed in OpenSSL doc/man3/d2i_X509.pod. Also add a RETURN VALUES section.
* Clarify X509_NAME stuff and cut back excessive references.schwarze2016-12-141-11/+8
| | | | | Ultimately, this page will have to be merged into X509_new(3), but we're not quite ready for that just yet.
* Make sure all manual pages discussing X509_NAME objectsschwarze2016-12-146-18/+29
| | | | | reference X509_NAME_new(3). Sparingly add a few other references to relevant X509_NAME*(3) pages while here.
* Complete rewrite to improve clarity.schwarze2016-12-141-61/+49
| | | | Add some cross references and STANDARDS.
* Document X509_NAME_ENTRY_new(3) and X509_NAME_ENTRY_free(3),schwarze2016-12-141-26/+74
| | | | | | | | | | | both listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.h. Note that the OpenSSL documentation specifies the wrong header file. Explain what X509_NAME_ENTRY represents. Simplify and clarify some wording. Sort parts of the text into a more logical order. Delete an irrelevant cross reference and add some relevant ones. Add a STANDARDS section.
* Write X509_NAME_new(3) manual from scratch. Both functions areschwarze2016-12-142-1/+83
| | | | | listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* tweak previous;jmc2016-12-142-7/+8
|
* New manuals ESS_SIGNING_CERT_new(3) and TS_REQ_new(3) writtenschwarze2016-12-143-1/+279
| | | | | | from scratch. All these functions are listed in <openssl/ts.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* Start RSA_PSS_PARAMS_new(3) stub from scratch. Both functionsschwarze2016-12-132-1/+54
| | | | | | are listed in <openssl/rsa.h> and OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. More could probably be said about PSS, but this is a start...
* tweak SEE ALSO; in particular,schwarze2016-12-139-36/+35
| | | | make sure that all PKCS7 pages point to PKCS7_new(3)
* Write PKCS7_new(3) manual page from scratch. All the functions areschwarze2016-12-132-1/+247
| | | | | public: listed in <openssl/pkcs7.h> and OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* typo fix; ok schwarzejmc2016-12-131-3/+3
|
* Write OCSP_CRLID_new(3) and OCSP_SERVICELOC_new(3) from scratch.schwarze2016-12-125-4/+196
| | | | | | | | | | | These two and OCSP_CRLID_free(3) and OCSP_SERVICELOC_free(3) are public by being in OpenSSL doc/man3/X509_dup.pod. OCSP_crlID_new(3) and OCSP_url_svcloc_new(3) are related and, even though completely undocumented in OpenSSL, obviously much more important. If you had told me a year ago that i would ever write such text, i would have called you crazy.
* various cleanup;jmc2016-12-124-25/+26
|
* Document OCSP_CERTID_new(3) listed in <openssl/ocsp.h> and in OpenSSLschwarze2016-12-121-16/+52
| | | | | | | | doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what the OCSP_CERTID object actually represents, along with the pertinent STANDARDS reference.
* Document OCSP_SINGLERESP_new(3), OCSP_SINGLERESP_free(3),schwarze2016-12-121-3/+90
| | | | | | | | | | OCSP_CERTSTATUS_new(3), OCSP_CERTSTATUS_free(3), OCSP_REVOKEDINFO_new(3), and OCSP_REVOKEDINFO_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference.
* Document OCSP_RESPONSE_new(3), OCSP_RESPONSE_free(3),schwarze2016-12-121-36/+144
| | | | | | | | | | | | OCSP_RESPBYTES_new(3), OCSP_RESPBYTES_free(3), OCSP_BASICRESP_new(3), OCSP_BASICRESP_free(3), OCSP_RESPDATA_new(3), OCSP_RESPDATA_free(3), OCSP_RESPID_new(3), and OCSP_RESPID_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference. Sort functions into a logical order and apply minor wording tweaks.
* Document OCSP_SIGNATURE_new(3), OCSP_SIGNATURE_free(3),schwarze2016-12-121-26/+95
| | | | | | | | | | | OCSP_REQINFO_new(3), OCSP_REQINFO_free(3), OCSP_ONEREQ_new(3), OCSP_ONEREQ_free(3), all in <openssl/ocsp.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file. Add some information about what these objects actually represent, along with the pertinent STANDARDS reference. Minor wording tweaks.
* Document DSAparams_dup(3). It is in <openssl/dsa.h> and documentedschwarze2016-12-121-2/+35
| | | | | | | | | | by OpenSSL, so it is clearly public. OpenSSL documents it in doc/man3/X509_dup.pod, but with wrong header file, wrong prototype, and misleading description. While here, fix the wrong d2i_DSA_SIG(3) return type and document those RETURN VALUES that i could easily figure out.
* Document DIRECTORYSTRING_new(3), DIRECTORYSTRING_free(3),schwarze2016-12-121-6/+32
| | | | | | | | | | | DISPLAYTEXT_new(3), DISPLAYTEXT_free(3). These functions are clearly public because OpenSSL documents them and they are in the public <openssl/asn1.h> header. OpenSSL documents these four functions in doc/man3/X509_dup.pod [sic], but the information given is completely wrong: wrong header file, wrong prototypes, misleading description. Why, oh why do people even bother to write documentation if nothing of what they write is true?
* import openssl.cnf(5) and x509v3.cnf(5) from OpenSSL;schwarze2016-12-116-14/+1259
| | | | below OpenBSD quality standards, but better than nothing...
* Distribute the text of ec(3) to the individual EC manuals where it belongs.schwarze2016-12-1111-107/+70
| | | | | | Make sure EC_GROUP_new(3) points to all EC manuals and all EC manuals point back to EC_GROUP_new(3), and add some other useful links as well. Change all links to ec(3) to point to EC_GROUP_new(3) instead.
* Merge all of rsa(3) into RSA_new(3).schwarze2016-12-113-93/+86
| | | | | In this case, keep the text about individual struct fields because it contains some actual information.
* Change all references to rsa(3) to point to RSA_new(3) instead.schwarze2016-12-1117-50/+51
| | | | Make sure all RSA pages point back to RSA_new(3).
* add missing section number to Xr;jmc2016-12-111-3/+3
|
* some fixes for the dsa.3 -> DSA_new.3 changes;jmc2016-12-113-9/+8
|
* Merge one sentence and the references from dsa(3) to DSA_new(3) andschwarze2016-12-103-80/+23
| | | | | | | discard the rest of the text. There is no value in documenting some of the fields of a structure and then going on to say that the structure is intended as opaque. Besides, i doubt that we want such strong marketing of ENGINE support.
* Change all references to dsa(3) to point to DSA_new(3).schwarze2016-12-1012-35/+33
| | | | Make sure all DSA pages point back to DSA_new(3).
* Merge one sentence and the references from dh(3) to DH_new(3) andschwarze2016-12-103-67/+12
| | | | | | | discard the rest of the text. There is no value in documenting some of the fields of a structure and then going on to say that the structure is intended as opaque. Besides, i doubt that we want such strong marketing of ENGINE support.
* Replace all references to dh(3) with DH_new(3).schwarze2016-12-1012-34/+30
| | | | Make sure that all DH pages point back to DH_new(3).
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-24 18:23:30 +0000