summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Write a new manual page X509_STORE_load_locations(3) from scratch.schwarze2017-01-071-1/+2
| | | | | | | | | | | Not documented by OpenSSL, but listed in <openssl/x509_vfy.h> and referenced from X509_LOOKUP_hash_dir(3), and clearly more important than the latter. Fixes three dead links reported by jmc@. Most of the information from SSL_CTX_load_verify_locations(3) should probably be moved here, but not all, since the SSL page also talks about SSL servers and clients and the like. As i'm not completely sure regarding the boundaries, i'm leaving that as it is for now.
* Write new d2i_ASN1_OCTET_STRING(3) manual page from scratch.schwarze2017-01-051-1/+2
| | | | | | All 36 functions listed in <openssl/asn1.h> and in OpenSSL doc/man3/d2i_X509.pod, six of them with wrong prototypes.
* Write new d2i_ASN1_SEQUENCE_ANY(3) manual page from scratch.schwarze2017-01-041-1/+2
| | | | | | | | All four functions are listed in <openssl/asn1.h> and in OpenSSL doc/man3/d2i_X509.pod. Note that in the OpenSSL documentation, three of the four prototypes are incorrect.
* Write d2i_ASN1_NULL(3) manual page from scratch.schwarze2016-12-291-1/+2
| | | | | | | | | | | Both functions are listed in <openssl/asn1.h> and in OpenSSL doc/man3/d2i_X509.pod. After reading the code, i'm not amused. You wouldn't think that it might take eight stack levels to decode a constant sixteen bit value that does not even allow a single content octet, or would you? Nota bene, this is an average of four stack levels for each non-zero bit decoded... :-(
* Write documentation for <openssl/x509v3.h> DER decoding andschwarze2016-12-281-1/+8
| | | | | encoding functions from scratch. All 46 functions are listed in OpenSSL doc/man3/d2i_X509.pod.
* Write new manual pages d2i_X509_ATTRIBUTE(3) and d2i_X509_EXTENSION(3)schwarze2016-12-281-1/+3
| | | | | from scratch. All six functions are listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
* Write new manual page d2i_PKCS8_PRIV_KEY_INFO(3) from scratch.schwarze2016-12-281-1/+2
| | | | | These six function are listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
* Write new manual pages d2i_OCSP_REQUEST(3) and d2i_OCSP_RESPONSE(3)schwarze2016-12-271-1/+3
| | | | | from scratch. All these functions are listed in <openssl/ocsp.h> and in OpenSSL doc/man3/d2i_X509.pod.
* New manual pages d2i_ESS_SIGNING_CERT(3) and d2i_TS_REQ(3) writtenschwarze2016-12-271-1/+3
| | | | | from scratch. All functions listed in <openssl/ts.h> and in OpenSSL doc/man3/s2i_X509.pod.
* Write the missing d2i_PKCS7(3) manual page from scratch.schwarze2016-12-261-1/+2
| | | | | | It is already referenced by one other manual page. All these functions are listed in <openssl/pkcs7.h> and in OpenSSL doc/man3/d2i_X509.pod.
* Write the missing d2i_PKCS12(3) manual page from scratch.schwarze2016-12-261-1/+2
| | | | | | It is already referenced from some other manuals. All these functions are listed in <openssl/pkcs12.h> and in OpenSSL doc/man3/d2i_X509.pod.
* Very carefully tweak OpenSSL doc/man3/d2i_X509.pod and create a newschwarze2016-12-241-1/+3
| | | | | | | | | | | | | | | | | | | | | | | ASN1_item_d2i(3) manual page from it. Enough text remains to keep Stephen Henson's Copyright. The eight functions documented in this new page are listed in <openssl/asn1.h> and in Symbols.list, so they are public even though OpenSSL does not document them. They are very important because hundreds of documented, much-used public interface functions are trivial wrappers around them, sharing their complicated semantics and their copious CAVEATS and BUGS. The plan is for the many pages documenting the wrappers to become very concise, to focus on the few type-dependent specifics, and to point to this new page for the details of the semantics, for the CAVEATS, and for the BUGS. While here, write a companion page ASN1_item_new(3) from scratch. The user interface described in that page scares the hell out of me, and i think people writing code to handle ASN.1 ought to be aware of that dangerous user interface design, or they will sooner or later get trapped.
* Write new SXNET_new(3) manual page from scratch. All four functionsschwarze2016-12-241-1/+2
| | | | | | | | | | | | | | | | are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file. I consider the quotation from http://www-03.ibm.com/security/library/wp_pki0730.shtml fair use because (1) it is a very brief extract from a long text, (2) no other source of information is available, (3) it is quoted for the purpose of education and research, (4) republishing happens in a not-for-profit context. I'm not including the URI into the manual page because large corporate websites are notorious for changing URIs during each spring cleaning.
* Write new PKEY_USAGE_PERIOD_new(3) manual page from scratch,schwarze2016-12-231-1/+2
| | | | | | | documenting the dubious RFC 3280 PrivateKeyUsagePeriod extension. Both functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write RFC 3820 manual page PROXY_POLICY_new(3) from scratch.schwarze2016-12-231-1/+2
| | | | | | These four functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write ACCESS_DESCRIPTION_new(3) manual page from scratch.schwarze2016-12-231-1/+2
| | | | | | All four functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new EXTENDED_KEY_USAGE_new(3) manual page from scratch.schwarze2016-12-231-1/+2
| | | | | | Both functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new POLICYINFO_new(3) manual page from scratch; i can't say thatschwarze2016-12-231-1/+2
| | | | | | i particularly like these fourteen functions, but they are all listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new NAME_CONSTRAINTS_new(3) manual page from scratch.schwarze2016-12-231-1/+2
| | | | | | These functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new BASIC_CONSTRAINTS_new(3) manual from scratch, explainingschwarze2016-12-231-1/+2
| | | | | | | the important point of how to distinguish CA certificates from end entity certificates. Both functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new DIST_POINT_new(3) manual page from scratch.schwarze2016-12-231-1/+2
| | | | | | All functions documented here are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new AUTHORITY_KEYID_new(3) manual page from scratch.schwarze2016-12-231-1/+2
| | | | | | Both functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write GENERAL_NAME_new(3) manual page from scratch - as if plain X.501schwarze2016-12-231-1/+2
| | | | | | | Name structures weren't already complicated enough, see X509_NAME_new(3). All these functions are listed in <openssl/x509v3.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Write new manual pages PKCS12_new(3) and PKCS12_SAFEBAG_new(3) fromschwarze2016-12-221-1/+3
| | | | | | | | | | | scratch. All these functions are listed in <openssl/pkcs12.h> and in OpenSSL doc/man3/X509_dup.pod. As usual, OpenSSL documentation specifies the wrong header file. Note that PKCS#12 documentation is still scanty at best. For example, out of 19 public functions handling PKCS12 objects, five are now documented, and this commit documents the first two out of 24 public functions handling PKCS12_SAFEBAG objects.
* Write X509_SIG_new(3) manual page from scratch. Both functions areschwarze2016-12-221-1/+2
| | | | | listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. OpenSSL documentation specifies the wrong header file.
* Delete the x509(3) manual page and merge what little content remainedschwarze2016-12-221-2/+1
| | | | into X509_new(3). Add information about STANDARDS.
* Stop installing the bn_dump(3) manual page.schwarze2016-12-221-2/+1
| | | | The functions documented there are no longer public.
* Write new PKCS8_PRIV_KEY_INFO_new(3) manual page from scratch.schwarze2016-12-221-1/+2
| | | | | | Both functions are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that OpenSSL documentation specifies the wrong header file.
* Write new X509_ATTRIBUTE(3) manual page from scratch.schwarze2016-12-171-1/+2
| | | | | | | | | | 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-171-1/+2
| | | | | | 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-161-1/+2
| | | | | | 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-161-1/+2
| | | | | | | 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-161-1/+2
| | | | | are listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* Write X509_NAME_new(3) manual from scratch. Both functions areschwarze2016-12-141-1/+2
| | | | | listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* New manuals ESS_SIGNING_CERT_new(3) and TS_REQ_new(3) writtenschwarze2016-12-141-1/+3
| | | | | | 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-131-1/+2
| | | | | | 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...
* Write PKCS7_new(3) manual page from scratch. All the functions areschwarze2016-12-131-1/+2
| | | | | public: listed in <openssl/pkcs7.h> and OpenSSL doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies the wrong header file.
* Write OCSP_CRLID_new(3) and OCSP_SERVICELOC_new(3) from scratch.schwarze2016-12-121-1/+3
| | | | | | | | | | | 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.
* import openssl.cnf(5) and x509v3.cnf(5) from OpenSSL;schwarze2016-12-111-2/+4
| | | | below OpenBSD quality standards, but better than nothing...
* Distribute the text of ec(3) to the individual EC manuals where it belongs.schwarze2016-12-111-2/+1
| | | | | | 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-111-2/+1
| | | | | In this case, keep the text about individual struct fields because it contains some actual information.
* Merge one sentence and the references from dsa(3) to DSA_new(3) andschwarze2016-12-101-2/+1
| | | | | | | 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.
* Merge one sentence and the references from dh(3) to DH_new(3) andschwarze2016-12-101-2/+1
| | | | | | | 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.
* Merge bn(3) into BN_new(3).schwarze2016-12-101-2/+1
| | | | | | | OpenSSL removed bn(3) without replacement, but the introductory text does seem helpful, and it is good for a sub-library to have a central page pointing to all other pages and pointed at from all other pages of the sub-library.
* We don't want section 3 manual pages with names that do not correspondschwarze2016-12-061-2/+1
| | | | | | | | | to functions, so delete the BIO(3) manual page and merge its content into BIO_new(3) and BIO_push(3). Sort the content of BIO_new(3) into a logical order and improve the wording in various ways. Add the required cross references to BIO_push(3).
* import d2i_PrivateKey(3) from OpenSSLschwarze2016-12-051-1/+2
|
* import the relevant parts of six more X509 manuals from OpenSSLschwarze2016-12-051-1/+7
|
* import the relevant parts of X509_STORE_get0_param(3) from OpenSSL, butschwarze2016-12-051-1/+2
| | | | since we don't have that function, call the page X509_STORE_set1_param(3)
* import three X509_check_*(3) manuals from OpenSSLschwarze2016-12-051-1/+4
|
* import X509_PUBKEY_new(3) from OpenSSLschwarze2016-12-051-1/+2
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-27 04:53:27 +0000