summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
* In rsa.h rev. 1.38 2018/03/17 15:12:56 and dsa.h rev. 1.30 2018/03/17schwarze2018-03-181-1/+3
| | | | | | 15:19:12, tb@ provided a subset of the DSA_meth_*(3) and RSA_meth_*(3) functions. Merge the relevant parts of the manual pages from OpenSSL, heavily tweaked by me, in particular for conciseness.
* In crypto.h rev. 1.43 and ssl.h rev. 1.153 2018/03/17 16:20:01, beck@schwarze2018-03-171-1/+2
| | | | | | provided OPENSSL_init_crypto(3) and OPENSSL_init_ssl(3). Write the documentation from scratch because the text OpenSSL provides is full of bloat.
* Two new manual pages OPENSSL_sk_new(3) and STACK_OF(3), written fromschwarze2018-03-011-1/+3
| | | | scratch, tweaks and OK jsing@ and jmc@.
* In x509_vfy.h rev. 1.23 2018/02/22 17:17:09, jsing@ providedschwarze2018-02-251-1/+2
| | | | | | | X509_OBJECT_get0_X509(3) and X509_OBJECT_get0_X509_CRL(3). Since they are undocumented in OpenSSL, write a new manual page from scratch, also documenting five closely related public functions that have already been available before.
* In x509_vfy.h rev. 1.22 2018/02/22 17:15:09, jsing@ providedschwarze2018-02-251-1/+2
| | | | | | X509_STORE_up_ref(3). X509_STORE_new(3) and X509_STORE_free(3) have already been available earlier. Import the documentation from OpenSSL, adding some precision.
* In bio.h rev. 1.32 2018/02/18 12:58:25, tb@ providedschwarze2018-02-191-1/+2
| | | | | BIO_get_data(3), BIO_set_data(3), and BIO_set_init(3). Import the documentation from OpenSSL.
* In x509.h rev. 1.29 2018/02/17 15:50:42, jsing@ providedschwarze2018-02-191-2/+2
| | | | | | X509_get0_signature(3). Merge the documentation from OpenSSL. Rename the file from X509_get_signature_nid.3 to X509_get0_signature.3 for consistency because we are not losing any history yet.
* In bio.h rev. 1.31 2018/02/17 13:57:14, tb@ provided new functionsschwarze2018-02-171-1/+2
| | | | | BIO_meth_*(). Import the documentation from OpenSSL, with extensive tweaks by me.
* Merge documentation for {DH,DSA}_get0_{key,pqg}(3),schwarze2018-02-171-1/+4
| | | | | EVP_PKEY_get0_{DH,DSA,RSA}(3), and RSA_{g,s}et0_key(3) that tb@ just provided.
* Import the new manual page EVP_PKEY_meth_new(3) from OpenSSL,schwarze2018-02-151-1/+2
| | | | removing parts that don't apply to OpenBSD.
* Import the new manual page EVP_PKEY_asn1_get_count(3) from OpenSSL,schwarze2018-02-151-1/+2
| | | | fixing half a dozen bugs and typos and also tweaking the wording a bit.
* In x509.h rev. 1.28 2018/02/14 16:57:25, jsing@schwarze2018-02-151-1/+2
| | | | | | | | | | | | provided X509_get0_notBefore(3) and its three friends. Write a manual page from scratch because what OpenSSL has is confusing and incomplete. By the way, providing two identical functions differing only in the constness of the returned structure is crazy. Are application programmers expected to be too stupid to write const ASN1_TIME *notBefore = X509_getm_notBefore(x) if that's what they want?
* In x509.h rev. 1.27 2018/02/14 16:18:10, jsing@ providedschwarze2018-02-141-1/+2
| | | | | X509_get_signature_nid(3). Add a new manual page for it based on the relevant parts of OpenSSL X509_get0_signature.pod.
* New manual page EVP_PKEY_asn1_new(3) from Richard Levitteschwarze2018-02-141-1/+2
| | | | | | | | | | | via OpenSSL commit 751148e2 Oct 27 00:11:11 2017 +0200, including only the parts related to functions that exist in OpenBSD. The design of these interfaces is not particularly pretty, they are not particularly easy to document, and the manual page does not look particularly good when formatted, but what can we do, things are as they are...
* New manual page X509_check_private_key(3), using informationschwarze2017-08-201-1/+2
| | | | | | | | from the OpenSSL manual and from code inspection. Use my own Copyright and license because no Copyright-worthy amount of text from OpenSSL remains. And, no, these functions do *NOT* check private keys, not at all.
* import PEM_bytes_read_bio(3) from OpenSSL,schwarze2017-08-201-1/+2
| | | | dropping the secmem stuff that we don't want
* import EVP_PKEY_meth_get_count.pod from OpenSSL, pruning the functions weschwarze2017-08-201-1/+2
| | | | don't have, which implies renaming the file to EVP_PKEY_meth_get0_info.3
* New ASN1_STRING_TABLE_add(3) manual page, based on information fromschwarze2017-08-201-1/+2
| | | | | | | | | the OpenSSL manual page committed on July 27, 2017, and on source code inspection. Use my own Copyright and license because no copyright-worthy amount of text from OpenSSL remains. NOTA BENE: BUGS Most aspects of the semantics considerably differ from OpenSSL.
* new X25519(3) manual page;schwarze2017-04-101-1/+2
| | | | from Dr. Stephen Henson <steve@openssl.org>, OpenSSL commit d218f3c3
* merge new UI documentation from OpenSSLschwarze2017-03-261-1/+4
|
* document X509_Digest(3) and friends;schwarze2017-03-251-1/+2
| | | | from Rich Salz <rsalz@openssl.org>, OpenSSL commit 3e5d9da5 etc.
* document the public function X509_cmp_time(3);schwarze2017-03-251-1/+2
| | | | | from Emilia Kasper <emilia@openssl.org>, OpenSSL commit 80770da3, tweaked by me
* OpenSSL documented the public function BIO_printf(3) (and friends)schwarze2017-03-251-1/+2
| | | | | in commit 2ca2e917. Document it here, too, but do not use their text. Be more concise and more precise at the same time.
* Mark ERR_add_error_data and ERR_add_error_vdata as not for internal use,beck2017-02-201-1/+2
| | | | | and document ERR_asprintf_error_data as their replacement. ok jsing@, ingo@
* Document functions returning standard moduli for DH key exchange.schwarze2017-01-311-1/+2
| | | | jsing@ confirmed that these are public and worth documenting.
* Document BN_set_flags(3) and BN_get_flags(3).schwarze2017-01-301-1/+2
| | | | jsing@ confirmed that these macros are public and worth documenting.
* 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.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2026-02-09 01:42:57 +0000