summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Rename the file PEM_X509_INFO_read.3 to PEM_X509_INFO_read_bio.3schwarze2025-07-171-2/+2
| | | | | because PEM_X509_INFO_read(3) no longer exists. Requested by tb@.
* Undocument PEM_X509_INFO_read(3), X509_PKEY_new(3) and X509_PKEY_free(3)schwarze2025-07-161-2/+1
| | | | because tb@ removed them from Symbols.list rev. 1.220 today.
* The functions SMIME_read_ASN1(3) and SMIME_write_ASN1(3)schwarze2025-06-111-3/+1
| | | | | are no longer public, so delete their manual pages. OK tb@
* Retire the manual pages OPENSSL_load_builtin_modules(3) and OBJ_NAME_add(3)schwarze2025-06-091-3/+1
| | | | | because these functions no longer exist. OK tb@
* Rework EC documentationtb2025-04-251-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | This replaces the giant, poor quality and outdated EC_GROUP_copy.3, EC_GROUP_new.3, and EC_POINT_new.3 manuals with seven new manuals written from scratch. * EC_GROUP_new_by_curve_name() is the entry point for builtin curves, * EC_GROUP_new_curve_GFp() describes lower level API that should not usually be needed apart from a handful of accessors. * EC_GROUP_check() contains two functions that applications should not need because either you know for certain something is an elliptic curve (so these checks are pointless) or you should not use it. * EC_GROUP_get_curve_name() describes some low level ASN.1 footguns and corresponding getters. * EC_POINT_new() contains the simple EC_POINT allocation and freeing API * EC_POINT_get_affine_coordinates() contains the coordinate accessors * EC_POINT_point2oct() is about encoding elliptic curve points While all this is quite far from perfect, the diff is getting too big and it will be easier to improve this in tree. It is definitely more repetitive than I would like it to be. Reviews, tweaks and general feedback are of course welcome. discussed with jsing
* Rename CRYPTO_get_mem_functions.3 to CRYPTO_set_mem_functions.3tb2025-03-081-2/+2
|
* Remove EC_GFp_* and EC_METHOD_get_field_type docstb2025-03-081-2/+1
|
* new manual page a2i_ipadd(3) written from scratchschwarze2024-12-271-1/+2
|
* new manual page v2i_ASN1_BIT_STRING(3) written from scratchschwarze2024-12-241-1/+2
|
* new manual page X509V3_parse_list(3) written from scratchschwarze2024-12-231-1/+2
|
* Move the horrific EVP_aes_128_ccm(3) API out of the important,schwarze2024-12-201-1/+2
| | | | | | | | | | | | algorithm-independent EVP_EncryptInit(3) manual as another step in making the latter leaner and more palatable. As a side benefit, the new EVP_aes_128_ccm(3) manual page may provide a better fighting chance to programmers who see themselves forced to support CCM for whatever reason. It documents the mandatory, but so far undocumented EVP_CTRL_CCM_GET_TAG control command and makes the description of the three EVP_CTRL_CCM_SET_* control commands and the numerous related quirks more precise.
* New manual page EVP_aes_128_gcm(3).schwarze2024-12-171-1/+2
| | | | | | | | | | | | The main benefit is moving the cumbersome and error-prone method of using EVP_EncryptInit(3) for AES-GCM out of the important, but obese manual page EVP_EncryptInit(3), and to create a logical place for pointing readers to the safer and more flexible EVP_AEAD_CTX_init(3). As a side benefit, document three control commands that were so far undocumented and make the description of three others more precise. Feedback and OK tb@.
* Move the algorithm-specific functions EVP_rc2_*(3) out of EVP_EncryptInit(3)schwarze2024-12-081-1/+3
| | | | | | | | | and document them properly in their own manual page, including the control commands EVP_CTRL_SET_RC2_KEY_BITS and EVP_CTRL_GET_RC2_KEY_BITS that were so far undocumented. Arguably, the main benefit is another small step making the important, but still obese EVP_EncryptInit(3) manual page more palatable.
* Delete the manual pages EVP_PKEY_meth_new(3) and EVP_PKEY_meth_get0_info(3)schwarze2024-12-061-3/+1
| | | | | | | | because tb@ deleted almost all functions documented there from the API in evp.h 1.127 on March 2 this year, but move the functions EVP_PKEY_CTX_set_data(3) and EVP_PKEY_CTX_get_data(3) that we still support to EVP_PKEY_keygen(3), because that page already documents EVP_PKEY_CTX_set_app_data(3) and EVP_PKEY_CTX_get_app_data(3).
* Delete the manual page EVP_PKEY_check(3).schwarze2024-12-061-2/+1
| | | | | All three functions documented in this page were deleted from the API by tb@ in evp.h rev. 1.136 on August 31 this year.
* Delete the manual page EVP_PKEY_asn1_new(3).schwarze2024-12-061-2/+1
| | | | | All the functions documented in this page were deleted from the API by tb@ in evp.h rev. 1.126 on March 2 this year.
* Link the new manual page EVP_PKEY_new_CMAC_key(3) to the buildschwarze2024-11-121-1/+2
| | | | | and purge the superseded information from the algorithm-independent page EVP_PKEY_new(3).
* remove duplicate X509v3_asid_add_id_or_range.3 linejsg2024-10-221-2/+1
|
* Remove X509_check_trust documentationtb2024-09-021-2/+1
|
* The X509at_* manuals are no longer neededtb2024-09-021-3/+1
|
* Remove documentation of EVP_whirlpooltb2024-08-291-2/+1
|
* LibreSSL no longer supports adding X.501 attributes to an EVP_PKEYtb2024-08-241-2/+1
| | | | Remove the corresponding documentation.
* Remove documentation of UI_UTIL_read_pw*tb2024-08-241-2/+1
| | | | | | | | According to some, a fail-open password verification function is par for the course for libcrypto. Unfortunately, we have been recommending its use over similarly named EVP functions after what amounted to a coin toss a few years back. Luckily enough, no one followed that advice and we can soon remove this API for good.
* Remove docs of various X509_TRUST "functionality" that no longer existstb2024-08-171-2/+1
| | | | | | | Some macros are still exposed, but apart from the loss of a very nice way of saying "this is completely misdesigned, overengineered and not properly thought through" the only thing we would have learned from it is that this stuff is "probably useless".
* link EVP_PKEY_CTX_set_tls1_prf_md.3 to buildtb2024-07-101-1/+2
|
* Install X509V3_EXT_get_nid.3tb2024-05-121-1/+2
|
* Remove CRL method API documentationtb2024-03-061-2/+1
|
* Remove ASN1_time_parse documentationtb2024-03-051-2/+1
|
* Remove EVP_MD_meth* documentationtb2024-03-051-2/+1
| | | | | Move the description of the EVP_MD_FLAGs to EVP_MD_nid() and add a reference to the CMS specification.
* Remove EVP_add_{cipher,digest}* docstb2024-03-041-2/+1
|
* Remove lh statstb2024-03-021-2/+1
| | | | | | | This could have been removed in an earlier bump. Now it's time for it to say goodbye. ok jsing
* Document various CMS_{signed,unsigned}_* functionsjob2024-01-221-1/+2
| | | | | | These functions change signed & unsigned attributes of a CMS SignerInfo object With & OK tb@
* Move DSA_generate_parameters.3 to DSA_generate_parameters_ex.3tb2023-12-291-2/+2
|
* Rename ASN1_STRING_TABLE_add manual to _gettb2023-12-161-2/+2
|
* EVP_EncryptInit(3) is among the most important "how to drive" manuals,schwarze2023-12-011-1/+2
| | | | | | | | but it is still excessively long and complicated. To reduce the amount of distractions a bit, split out three deprecated functions into a new manual page EVP_CIPHER_CTX_init(3). No text change. In part suggested by tb@, who agrees with the direction.
* Remove remaining ENGINE manualstb2023-11-191-11/+1
| | | | They document functionality that no longer exists.
* Document X509v3_{addr,asid}_validate_{path,resource_set}(3)tb2023-09-291-1/+2
| | | | | | | These were the last four RFC 3779 things that check_complete.pl x509v3 complained about. I will surely tweak and try to improve a few things in the coming days, but the pages should now be stable enough that review efforts will likely not be wasted. Any feedback appreciated.
* Document X509v3_{addr,asid}_subset.3tb2023-09-281-1/+2
| | | | | | First RFC 3779 page without a BUG section. It could have one, but I'm in a lenient mood right now. Maybe it's just that this is bad but not quite as bad as EVP.
* Document X509v3_{addr,asid}_inherits(3)tb2023-09-261-1/+2
| | | | Also note another bug in X509v3_asid_{canonize,is_canonical}(3).
* Document X509v3_addr_get_{afi,range}(3)tb2023-09-261-1/+3
|
* Document the guts of RFC 3779 IPAddrBlockstb2023-09-261-1/+2
| | | | Let's just say there's room for improvement...
* sorttb2023-09-251-2/+2
|
* New manual page documenting the usual four ASN.1 functions for bothtb2023-09-251-1/+2
| | | | ASRange and ASIdOrRange
* Add initial documentation for the RFC 3779 APItb2023-09-251-2/+5
| | | | | | | | This documents the part of the API that allows building the two extensions. It is all very complicated and the bug density is quite high. Surely there's lots of room for improvement, but I've been sitting way too long on versions of these. I'll never finish. Let's fix and improve in tree.
* new manual page EVP_PKEY_CTX_get_operation(3),schwarze2023-09-091-1/+2
| | | | also documenting EVP_PKEY_CTX_get0_pkey(3)
* Split two new manual pages EVP_MD_nid(3) and EVP_MD_CTX_ctrl(3)schwarze2023-09-071-1/+3
| | | | out of the large EVP_DigestInit(3). No text change.
* Split three new manual pages EVP_CIPHER_nid(3), EVP_CIPHER_CTX_ctrl(3),schwarze2023-08-311-1/+4
| | | | | | | | | | | and EVP_CIPHER_CTX_set_flags(3) out of the excessively large and unwieldy EVP_EncryptInit(3). This causes a number of inaccuracies and gaps to stand out, but i'm not mixing text changes or content additions into this split. Using very useful feedback from tb@ regarding what belongs together and how important the various functions are. I refrained from bothering him with the complete patch, but he likes the general direction.
* Document EVP_{CIPHER,MD}_do_all{,_sorted}(3)tb2023-08-301-1/+2
| | | | | | | | | | The function prototypes in the SYNOPSIS don't look great, but schwarze assures me that this is how it is supposed to be. It is rather strange that OpenSSL chose to sprinkle OPENSSL_init_crypto() calls into these four functions rather than two inside OBJ_NAME_do_all{,_sorted}(3). Surely there was a good reason for that. With input and fixes from schwarze
* Move the weak SHA-1 and MD5 hashes out of EVP_DigestInit(3)schwarze2023-08-271-1/+2
| | | | | into a new EVP_sha1(3) manual page, and also mention EVP_md4(3) there. Using input from tb@ and jsing@, who like the general direction.
* In evp.h rev.s 1.90 and 1.97, tb@ provided EVP_CIPHER_CTX_get_cipher_data(3)schwarze2023-08-251-1/+2
| | | | | | and EVP_CIPHER_CTX_set_cipher_data(3). Import the manual page from the OpenSSL 1.1 branch, which is still under a free licence, with several improvements by me.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-26 01:40:03 +0000