summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* encoding -> decoding for d2itb2023-10-011-3/+3
|
* Reorder list of additional validation checks neededtb2023-09-301-9/+8
|
* Switch copyright year to 2023.tb2023-09-302-4/+4
| | | | | | | Apparently I should have used 2023 despite sharing versions of these files with several people under this license (and thus permitting them to redistribute and share with the public). It makes no sense to me, but shrug.
* Use addrblocks for .Fatb2023-09-301-2/+2
|
* avoid using the string "a" without markup as a placeholderschwarze2023-09-301-4/+9
| | | | | where that feels potentially confusing, and add one missing .Pp macro; no change of meaning
* consistently use "allow_inherit" for the argument nameschwarze2023-09-301-6/+6
| | | | and fix whitespace on one text line; no change of meaning
* drop one pair of needless parenthesesschwarze2023-09-301-5/+5
| | | | and polish one wording; no change of meaning
* remove a useless repetition of a function nameschwarze2023-09-301-6/+4
| | | | | that was also followed by a bogus argument, and fix one grammatical error; no change of meaning
* polish an awkward wordingschwarze2023-09-301-9/+7
| | | | | and capitalize "AFI" where is does not refer to the function argument; no change of meaning
* two instances of missing .Fa macrosschwarze2023-09-301-13/+15
| | | | and some missing escaping of HYPHEN-MINUS; no text change
* fix one copy and paste error: d2i_*() decode rather than encode;schwarze2023-09-301-7/+7
| | | | plus some minor markup and punctuation fixes
* garbage collect two stray words, no change of meaningschwarze2023-09-301-4/+4
|
* Some wording tweaks to make things a bit more precise.tb2023-09-291-6/+7
|
* Fix a wrong tag and work around an ugly linebreaktb2023-09-291-5/+6
|
* Document X509v3_{addr,asid}_validate_{path,resource_set}(3)tb2023-09-296-10/+217
| | | | | | | 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.3 take two (missed cvs add)tb2023-09-281-0/+176
| | | | | | 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}_subset.3tb2023-09-287-30/+40
| | | | | | 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.
* Various small tweaks in the RFC 3779 docstb2023-09-276-58/+69
| | | | Mention a few more bugs and unify manpage descriptions
* Document X509v3_{addr,asid}_inherits(3)tb2023-09-266-5/+140
| | | | Also note another bug in X509v3_asid_{canonize,is_canonical}(3).
* Document X509v3_addr_get_{afi,range}(3)tb2023-09-264-5/+142
|
* Document the guts of RFC 3779 IPAddrBlockstb2023-09-266-13/+534
| | | | Let's just say there's room for improvement...
* Missing variable name in prototypetb2023-09-261-2/+2
|
* Fix section title of X.690 reference (missing article)tb2023-09-261-3/+3
|
* Document some barely usable parts of the ASIdentifiers API.tb2023-09-263-18/+184
| | | | | Someone clearly didn't actually use much of the code they wrote and exposed and therefore didn't think it through properly.
* sorttb2023-09-251-2/+2
|
* New manual page documenting the usual four ASN.1 functions for bothtb2023-09-254-3/+263
| | | | ASRange and ASIdOrRange
* tweak wording and fix a typotb2023-09-251-3/+3
|
* Tiny tweaks: missing article, capitalize a word and change an Xrtb2023-09-252-5/+5
|
* Document the RFC 3779 extensions as supportedtb2023-09-251-2/+5
|
* Add initial documentation for the RFC 3779 APItb2023-09-255-5/+889
| | | | | | | | 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.
* PEM_def_callback(3) does not truncate its argument but merely the copy,schwarze2023-09-181-15/+21
| | | | plus a few wording improvements
* Rewrite RSA_get_ex_new_index(3) and CRYPTO_set_ex_data(3) from scratch.schwarze2023-09-182-462/+753
| | | | | | | | | The defects of the old pages were too numerous to list in full but included vagueness, gaps, misleading statements, bad ordering, and duplication. Use my Copyright since none of the text we inherited from OpenSSL remains. Without doing a thorough review, tb@ thinks he likes the new pages after quickly reading through both of them.
* replace the outdated statement that everything uses SHA-1schwarze2023-09-131-5/+33
| | | | by a table showing the supported algorithms
* Document the special meaning of NID_undef in this context.schwarze2023-09-131-4/+13
| | | | | | | | From Matt Caswell <matt at openssl dot org> via OpenSSL commit 1212818e (Sep 11, 2018) from the OpenSSL 1.1 branch, which is still under a free license. Wording slightly tweaked by me.
* Various improvements:schwarze2023-09-131-15/+63
| | | | | | | | * Document the ASN1_PKEY_CTRL_DEFAULT_MD_NID control operation. * Mention that EVP_PKEY_asn1_new(3) sets ASN1_PKEY_DYNAMIC. * Fix the description of EVP_PKEY_asn1_copy(3), which was totally wrong. * Warn about the crazy ASN1_PKEY_DYNAMIC handling in EVP_PKEY_asn1_free(3). * Be more precise about EVP_PKEY_asn1_new(3) RETURN VALUES.
* document the EVP_PKEY_ASN1_METHOD flagsschwarze2023-09-131-5/+51
| | | | ASN1_PKEY_ALIAS, ASN1_PKEY_DYNAMIC, and ASN1_PKEY_SIGPARAM_NULL
* minor markup fixes: add one missing .Dv and one missing .Vt macroschwarze2023-09-131-4/+8
|
* document the EVP_PKEY_CTRL_MD and EVP_PKEY_CTRL_GET_MD command constantsschwarze2023-09-131-4/+35
|
* fix typoschwarze2023-09-121-2/+2
|
* document the four EVP_PKEY_OP_TYPE_* mask constantsschwarze2023-09-121-4/+23
|
* document sizes for ED25519 and X25519,schwarze2023-09-121-6/+19
| | | | including the constants ED25519_KEYLEN and X25519_KEYLEN
* document the constant EVP_CHACHAPOLY_TLS_TAG_LENschwarze2023-09-122-3/+9
|
* Document EVP_AEAD_DEFAULT_TAG_LENGTH and EVP_AEAD_MAX_TAG_LENGTH,schwarze2023-09-121-5/+20
| | | | making some adjacent wordings slightly more precise.
* fix the vague and misleading description of the EVP_MD_FLAG_* constantsschwarze2023-09-121-22/+72
|
* spellingjsg2023-09-111-3/+3
|
* Mention EVP_PKEY_encrypt_old(3) and EVP_PKEY_decrypt_old(3) becauseschwarze2023-09-101-7/+87
| | | | | | | some software still calls them. Put them here because despite the function and header names, they are really specific to RSA. Besides, this avoids a distraction in the more important EVP_PKEY_encrypt(3) and EVP_PKEY_decrypt(3) manual pages.
* Briefly mention SSLeay_add_all_algorithms(3) becauseschwarze2023-09-101-6/+18
| | | | | | | | surprisingly large numbers of software packages still call it. Mark the unused aliases OPENSSL_add_all_algorithms_conf(3), OPENSSL_add_all_algorithms_noconf(3), SSLeay_add_all_ciphers(3), and SSLeay_add_all_digests(3) as intentionally undicumented.
* Document the deprecated functions EVP_set_pw_prompt(3) andschwarze2023-09-101-71/+86
| | | | | | | | | | | | | | | | EVP_get_pw_prompt(3) because some software out there still uses them. While here, also improve the description of EVP_read_pw_string(3). Delete documentation for des_read_pw(3) and des_read_pw_string(3). They couldn't be used in LibreSSL since at least 2016 because they were never in Symbols.list, and in 2022, jsing@ also removed them from <openssl/ui_compat.h>. Delete the misleading AUTHORS section. Richard Levitte did not write the original implementation of these functions, and the compatibility wrapper around the UI_process(3) API that he did write is not notable enough to be mentioned so prominently.
* Mark EVP_ENCODE_LENGTH() and EVP_DECODE_LENGTH() as intentionallyschwarze2023-09-101-2/+6
| | | | | | | undocumented because they do not describe properties of the Base64 encoding but add arbitrary constant lengths, hence being implementation details of BIO_f_base64(3). Besides, they are practically unused outside evp/bio_b64.c.
* fix Xr punctuationjsg2023-09-101-3/+3
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-27 05:01:55 +0000