summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Below STANDARDS, reference the two most relevant sections of RFC 5652.schwarze12 days1-1/+5
| | | | | | | | Given that RFC 5652 does not override the earlier (and simpler) standards but instead strives to remain compatible, referencing both the original and the latest versions seems helpful. OK tb@
* Update PKCS7_add0_attrib_signing_time() docstb12 days1-3/+3
| | | | | | | Document the change of behavor from pk7_attr.c r1.17: the time is now validated to be in correct RFC 5280 time format. ok kenjiro
* Rename the file PEM_X509_INFO_read.3 to PEM_X509_INFO_read_bio.3schwarze2025-07-172-5/+5
| | | | | because PEM_X509_INFO_read(3) no longer exists. Requested by tb@.
* Undocument the undocumentedness of BIO_s_log. It's gone.tb2025-07-161-3/+2
|
* Undocument PEM_X509_INFO_read(3), X509_PKEY_new(3) and X509_PKEY_free(3)schwarze2025-07-169-144/+31
| | | | because tb@ removed them from Symbols.list rev. 1.220 today.
* X509_sign: make variables in SYNOPSIS match the ones used in DESCRIPTIONtb2025-07-111-8/+8
|
* X509_get0_signature: call out inconsistent argument order in BUGStb2025-07-061-2/+9
| | | | | These annoying and careless inconsistencies were introduced when const was sprinkled everywhere without rhyme or reason.
* fix double word; ok tb@jsg2025-07-041-3/+3
|
* Const correct the documentation of EVP_PKEY_get{0,1}_{DH,DSA,EC_KEY,RSA}()tb2025-07-021-9/+9
|
* Fix documented EVP_PKEY{,_base}_id() signaturetb2025-07-021-4/+4
| | | | | These have been taking a const pkey ever since they were added in OpenSSL 1.0.0.
* X509_print_ex.3: document X509_FLAG_NO_IDStb2025-07-011-2/+7
| | | | ok job kenjiro
* Fix signature of BN_zerotb2025-06-141-5/+4
| | | | This was changed a bit more than two years ago.
* The mdoc(7) .Ft macro does not need quoting of its arguments, but aboutschwarze2025-06-1314-86/+86
| | | | | | | 10% of our manual pages using this macro employed useless quoting anyway. Remove these quotes such that they do not incite fear, uncertainty, and doubt in developers who happen to look at these pages. jmc@ and tb@ agree with the direction.
* Bring the DESCRIPTION a bit closer to reality, in particular stopschwarze2025-06-121-7/+31
| | | | | | | | claiming that the "add" functions add anything. Indicate that they are mostly NOOPs nowadays, but without being overly specific. Also, more explicitly discourage abusing OpenSSL_add_all_algorithms(3) for loadiing a configuration file. Guidance and OK tb@.
* EC_GROUP_check: rephrase a sentence so it's a bit less awkwardtb2025-06-111-5/+7
|
* The functions SMIME_read_ASN1(3) and SMIME_write_ASN1(3)schwarze2025-06-113-290/+1
| | | | | are no longer public, so delete their manual pages. OK tb@
* Since the function SMIME_write_ASN1(3) is no longer public, move theschwarze2025-06-112-63/+181
| | | | | | | descriptions of CMS_REUSE_DIGEST, PKCS7_REUSE_DIGEST, SMIME_BINARY, and SMIME_CRLFEOL and some improved wordings from that former page to SMIME_write_CMS(3) and SMIME_write_PKCS7(3), with some further polishing. Feedback and OK tb@.
* Lie less below RETURN VALUES, add a related BUGS entry,schwarze2025-06-112-10/+24
| | | | | | and since SMIME_write_ASN1(3) is no longer public, replace the .Xr to it with some other pointers. OK tb@
* SMIME_read_ASN1(3) and SMIME_write_ASN1(3) are no longer public,schwarze2025-06-114-12/+18
| | | | | | so link to SMIME_read_CMS(3), SMIME_read_PKCS7(3), SMIME_write_CMS(3), and/or SMIME_write_PKCS7(3) instead; OK tb@
* SMIME_read_ASN1(3) is no longer public,schwarze2025-06-112-6/+12
| | | | | | so link to SMIME_read_CMS(3) or SMIME_read_PKCS7(3) instead, and sprinkle a few other .Xrs that may be helpful; OK tb@
* Retire the manual pages OPENSSL_load_builtin_modules(3) and OBJ_NAME_add(3)schwarze2025-06-097-456/+25
| | | | | because these functions no longer exist. OK tb@
* EVP_cleanup(3) is no longer relevant here since it no longer has any effect.schwarze2025-06-091-3/+2
| | | | OK tb@
* mention that SSL_load_error_strings(3) lives in libssl;schwarze2025-06-081-1/+3
| | | | "sounds good" tb@
* .Lb libcrypto ; OK tb@schwarze2025-06-08411-822/+1233
|
* remove some "intentionally undocumented" comments regarding stuffschwarze2025-06-089-37/+27
| | | | | that no longer exists, and add .Lb; OK tb@
* add the missing .In line and add .Lb libcrypto ; OK tb@schwarze2025-06-082-4/+8
|
* EC_POINT_new: wording tweaks in the BUGS sectiontb2025-05-181-6/+6
|
* Garbage collect docs of BIO_dump{,_indent}_{cb,fp}()tb2025-05-091-35/+3
| | | | | The _cb() variants were only documented as intentionally undocumented. Be that as it may, they left the building more than a year ago.
* Fix up two markup mistakes with .Fn and .Xrtb2025-05-041-4/+4
|
* More space around .Dl + a typo on toptb2025-05-012-5/+11
|
* EC_GROUP_check.3: rephrase a sentence to avoid a word repetitiontb2025-04-281-4/+4
|
* EC_GROUP_new_by_curve_name.3: escape a - in code.tb2025-04-281-3/+3
|
* EC_POINT_point2oct: remove in_ prefix in RETURN VALUEStb2025-04-261-5/+5
|
* EC_GROUP_new_curve_GFp: some fixes in the RETURN VALUE sectiontb2025-04-261-9/+12
|
* Fix markup for EC_GROUP_set_point_conversion_formtb2025-04-261-4/+5
|
* Fix up a few dangling referencestb2025-04-254-13/+12
|
* Rework EC documentationtb2025-04-2513-1242/+1998
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* BN_new: zap an anachronistic admonitiontb2025-04-251-4/+2
| | | | | | | | | -This type should be considered opaque and fields should not be modified -or accessed directly. The type has long been opaque and reasonable people will not do things that permit them to access the fields of opaque types directly. Of course, in the vicinity of OpenSSL code and API all sorts of insanity actually exist.
* Use hyphenated spelling for the SHAs except for the APItb2025-04-1712-41/+42
| | | | | The mix of SHA256 and SHA-256 is jarring, so use FIPS's spelling. Leave HMAC-SHA256 as it is and fix a nearby RIPEMD-160.
* Fix RETURN VALUES for EVP_CIPHER_CTX_ctrl(3)tb2025-03-251-9/+4
| | | | | | | | | | | | | | | The current documentation was clearly incorrect since a return of -1 from the methods is explicitly intercepted and translated to 0. schwarze and I both audited the tree and concluded that only 0 and 1 is possible. OpenSSL 3 broke this API contract and now has explicit return -1 in the convoluted 200-line maze this simple function has become with recent provider improvements. So add a small sentence hinting at that. Nobody will be surprised to read that with OpenSSL's characteristic penchant for needless inconsistency the return value checks in their tree are all over the place and sometimes incorrect. ok schwarze (with two tweaks)
* Rename a bunch of confusingly named variablestb2025-03-151-6/+6
| | | | | | Variables of the type serialized or deserialized are called val_in or val_out in all other manuals, so align this page to using those rather than the confusing X509_CRL **der_out, etc.
* const correct d2i_* prototypestb2025-03-144-13/+13
|
* X509_NAME_print_ex: zap stray commatb2025-03-091-2/+2
|
* Fix documented signature of UI_OpenSSL()tb2025-03-091-3/+3
|
* Fix documented signature of BN_MONT_CTX_copy()tb2025-03-091-3/+3
|
* X509_NAME_print_ex.3: move s to the proper placetb2025-03-091-2/+2
|
* Remove mention of X509_NAME_print(3) in the docstb2025-03-093-46/+13
|
* Adjust signature of CRYPTO_set_mem_functions and remove _get_ docstb2025-03-081-23/+5
|
* Rename CRYPTO_get_mem_functions.3 to CRYPTO_set_mem_functions.3tb2025-03-082-4/+4
|
* Remove EC_POINT_method_of() docstb2025-03-081-19/+1
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-08 07:56:48 +0000