summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* document BN_zero_ex(3)schwarze2021-12-191-6/+38
|
* Put CTLOG and SCT stacks definitions in the right place.jsing2021-12-191-47/+49
| | | | No functional change.
* Document BN_abs_is_word(3).schwarze2021-12-181-5/+21
| | | | | | | | | | | | | | | | | | | | | | | | While here, add the missing "const" qualifier to the second parameter of BN_is_word(3) - even though i doubt that marking an integral type parameter as "const" serves any significant purpose... Note that the OpenSSL documentation for this function that Billy Brumley committed on August 4, 2021 is actually wrong. Essentially, it says "BN_abs_is_word() test[s] if a equals ... |w|." Now pray tell me, what exactly is the point of taking the absolute value of an unsigned integer number? To compensate for the obvious absurdity of his patch, Billy made a point of getting *three* OKs from rather notable people: Pauli Dale, Nicola Tuveri, and Dmitry Belyavskiy. I believe this is a striking example of the cavalier attitude some projects put on display when it comes to documentation, and also a striking example of how bad documentation can occasionally be worse than no documentation at all, because the OpenSSL manual page will now thoroughly confuse anyone reading it. SCNR pointing out this (hopefully unintentional) hilarity - or is this an attempt at trolling the readers of their documentation? If it is, they certainly got me.
* add the missing .Nm BN_get_rfc3526_prime_1536,schwarze2021-12-181-2/+3
| | | | fixing a minibug found with check_complete.pl
* new manual page OBJ_add_sigid(3)schwarze2021-12-189-19/+155
|
* KNF two commentstb2021-12-181-16/+16
|
* Reinstate the licenses that were replaced with a license stubtb2021-12-182-12/+108
| | | | in OpenSSL commit d2e9e320.
* Revert license stubs to full licenses in the remaining files.tb2021-12-183-21/+164
|
* Reinstate the license stubs to their original licenses in most of thetb2021-12-1810-57/+537
| | | | | | files in libcrypto/ct. This reverts OpenSSL commit d2e9e320 discussed with jsing
* Convert o2i_SCT* functions to CBS.jsing2021-12-182-151/+149
| | | | | | This provides cleaner and safer code. ok inoguchi@ tb@
* Rename argument to SCT_LIST_free()jsing2021-12-181-3/+3
|
* new manual page OBJ_NAME_add(3)schwarze2021-12-175-9/+363
|
* mention lh_strhash(3) in the NAME, SYNOPSIS, and HISTORY sections;schwarze2021-12-171-10/+20
| | | | while here, repair a typo in the lh_retrieve(3) synopsis
* alphabetical order is hard, tb...tb2021-12-171-2/+2
|
* fix indenttb2021-12-171-2/+2
|
* document obj_cleanup_defer(3) and check_defer(3)schwarze2021-12-162-8/+72
|
* document OBJ_new_nid(3), OBJ_add_object(3), and OBJ_create_objects(3);schwarze2021-12-151-9/+91
| | | | mark OBJ_create_and_add_object() as intentionally undocumented
* Move OBJ_create(3) into its own manual pageschwarze2021-12-155-63/+157
| | | | | because OBJ_nid2obj(3) is already long and more functions related to OBJ_create(3) have to be documented.
* Rename asn1_lib.c to asn1_old_lib.cjsing2021-12-152-3/+3
| | | | | | | This will allow us to add a new asn1_lib.c while replacing the code that is in currently in asn1_old_lib.c. Discussed with tb@
* Sync bytestring with libssl.jsing2021-12-154-4/+151
|
* Consolidate various ASN.1 code.jsing2021-12-159-650/+465
| | | | | | | | | Rather than having multiple files per type (with minimal code per file), use one file per type (a_<type>.c). No functional change. Discussed with tb@
* unifdef -U CRYPTO_MDEBUG -m tasn_new.cjsing2021-12-151-33/+1
|
* Document i2c_ASN1_INTEGER(3).schwarze2021-12-151-7/+46
| | | | | | | | | | | | | While it was probably a mistake that steve@ made some i2c_*() and c2i_*() functions public back in 2000 and while we would like to delete them from the API, it may not be possible to delete this particular function because in contrast to the others (which are already marked as intentionally undocumented), this one is used by various real-world software, so for now, explain what it does, just in case people find it in existing code. While here, use the familiar term "byte" that we generally use throughout all our manual pages, even though the ASN.1 standard uses the term "octet" instead, which is more precise only in theory.
* forgotten .Dv macros in -column listsschwarze2021-12-142-19/+19
|
* add roff(7) comments listing some M_ASN1_* aliasesschwarze2021-12-143-6/+11
| | | | that are intentionally undocumented
* Consolidate ASN.1 universal tag type data.jsing2021-12-146-82/+283
| | | | | | | | | | | | There are currently three different tables in three different files that contain information about ASN.1 universal class tag types. Range checking is also implemented in three different places (with different implementations). Consolidate all of this into a single table, provide a lookup function that deals with the range checks and wrappers to deal with specific types. ok inoguchi@ tb@
* document the very quirky behaviour of the SMIME_OLDMIME flagschwarze2021-12-141-3/+39
|
* new manual page SMIME_text(3)schwarze2021-12-144-5/+65
|
* new manual page SMIME_read_ASN1(3)schwarze2021-12-144-8/+134
| | | | using parts of the text from SMIME_read_CMS(3) and SMIME_read_PKCS7(3)
* new manual page PEM_write_bio_ASN1_stream(3);schwarze2021-12-135-6/+100
| | | | | certainly not perfect, but arguably better than the even terser PEM_write_bio_CMS_stream(3) and PEM_write_bio_PKCS7_stream(3)
* Remove the last internal use of d2i_ASN1_BOOLEAN.tb2021-12-131-7/+3
| | | | | | From Stephen Henson, OpenSSL 564df0dd ok jsing
* Clean up d2i_ASN1_BOOLEAN() and i2d_ASN1_BOOLEAN().jsing2021-12-133-118/+23
| | | | | | Convert these to templated ASN.1, given we already have ASN1_BOOLEAN_it. ok inoguchi@ tb@
* this file doesn't use anything from <stdio.h>;schwarze2021-12-131-2/+1
| | | | | in particular, NULL is also in <stdlib.h> according to the C99 standard; "free commit" tb@
* Convert asn1_d2i_ex_primitive()/asn1_collect() from BUF_MEM to CBB.jsing2021-12-131-31/+37
| | | | | | | | With this we get simpler code, overflow checking and more sensible memory ownership. Also switch the free_cont case to freezero() since this could contain secrets. ok inoguchi@ tb@
* new manual page SMIME_write_ASN1(3);schwarze2021-12-135-9/+179
| | | | still vague in various respects, but it's a start
* Catch integer overflow rather than silently truncating whileschwarze2021-12-131-1/+10
| | | | | | parsing MASK: strings in ASN1_STRING_set_default_mask_asc(3). Issue noticed by tb@, patch by me, two additional #include lines from tb@. OK tb@.
* new manual pages i2d_ASN1_bio_stream(3) and SMIME_crlf_copy(3)schwarze2021-12-136-8/+203
|
* Annotate the structs that will be moved to hmac_local.h and evp_locl.htb2021-12-123-8/+20
| | | | | | | | | | | | in an upcoming bump. This omits EVP_AEAD_CTX which will be dealt with separately. EVP_CIPHER_INFO internals are still publicly visible in OpenSSL, so it won't be moved. Move typedefs for HMAC_CTX and EVP_ENCODE_CTX to ossl_typ.h. These typedefs will be visible by files including only hmac.h or evp.h since hmac.h includes evp.h and evp.h includes ossl_typ.h. ok inoguchi
* Include evp_locl.h where it will be needed once most structs fromtb2021-12-1271-72/+184
| | | | | | evp.h will be moved to evp_locl.h in an upcoming bump. ok inoguchi
* Add a mostly empty hmac_local.h. HMAC_CTX and a few other thingstb2021-12-127-6/+86
| | | | | | | from hmac.h will be moved there in an umpcoming bump. Include this file where it will be needed. ok inoguchi
* Add -I${LIBCRYPTO_SRC}/hmac to CFLAGS. Needed in an upcoming commit.tb2021-12-121-1/+2
| | | | ok inoguchi
* Add header guards to evp_locl.h.tb2021-12-121-1/+6
| | | | ok inoguchi
* document the ub_* constantsschwarze2021-12-121-2/+22
|
* typoschwarze2021-12-121-2/+2
|
* New manual page providing a rudimentary description of BIO_new_NDEF(3).schwarze2021-12-124-5/+127
| | | | | | | The API surrounding this is so complicated and streaming is so rarely used in practice that describing this in more detail is not a priority right now. The documentation of the wrapper BIO_new_CMS(3) is also rather vague, and BIO_new_PKCS7() isn't described at all so far.
* Rewrite X509_ALGOR_set_md() without reaching into EVP_MD.tb2021-12-121-5/+3
| | | | ok inoguchi schwarze
* Merge two bugfixes in ASN1_STRING_TABLE_add(3) and ASN1_STRING_TABLE_get(3)schwarze2021-12-111-34/+58
| | | | | | | | | | | | | | | | | | | | | | from the OpenSSL 1.1.1 branch, which is still under a free license, mostly this commit: commit d35c0ff30b31be9fd5dcf3d552a16feb8de464bc Author: Dr. Stephen Henson <steve@openssl.org> Date: Fri Oct 19 15:06:31 2012 +0000 fix ASN1_STRING_TABLE_add so it can override existing string table values This fixes a segfault in ASN1_STRING_TABLE_add(3), which tried to change a static const entry when called with an nid already in the default table, and it switches the precedence of the two tables in ASN1_STRING_TABLE_get(3). In addition, it changes behaviour in the following minor ways: * Ignore negative minsize and maxsize arguments, not just -1. * Ignore a zero mask and zero flags. It's unclear whether these additional changes make the API absolutely better, but we want compatibility with OpenSSL in these functions. Tweaks & OK tb@.
* Merge the deletion of <ctype.h>, which isn't used here,schwarze2021-12-111-17/+21
| | | | | | | and some style improvements from the OpenSSL 1.1.1 branch, which is still under a free license. No functional change. OK and additional tweaks tb@.
* document STABLE_NO_MASK and STABLE_FLAGS_MALLOC,schwarze2021-12-111-13/+32
| | | | | mention which argument values can be used to not change the respective fields, and tweak a few additional wordings
* two more "the the" fixes;jmc2021-12-111-3/+3
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-28 09:36:39 +0000