summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Add aliases for AES AEAD constructions and ChaChatb2023-11-061-9/+12
| | | | | These used the wycheproofTestGroupAead type but an upcoming change requires to change this. Introduce the aliases now to make the next diff cleaner.
* Fix a for loop bug introduced in the concurrency refactortb2023-11-061-3/+4
| | | | | | | | | | | | | Due to Go's idiosyncratic semantics of for loops, tests would only run some of the test groups in the JSON file because by the time the closure is called, the array index could be changed. For example, on fast 8 core machines, the CMAC tests would run the last test group with key size 320 eight times rather than each of the eight test groups once. Make a copy of the pointer before passing it to the closure to avoid this issue. Simpler version of my initial fix from jsing
* Uncomment json webcrypto line. Packages will have caught up...tb2023-11-061-3/+2
|
* Provide prototype for X509_ALGOR_set_md()tb2023-10-261-1/+3
| | | | | | Once we remove X509_ALGOR_set_md() we can link this test statically and use X509_ALGOR_set_evp_md() but for now make sure the documented workaround for this garbage API works.
* Add a few more test cases for mod_exp aliasingtb2023-10-191-33/+78
|
* The bn_mod_exp test is no longer an expected failuretb2023-10-191-3/+1
|
* Add test case checking aliasing of the result with other argumentstb2023-10-192-2/+108
| | | | | These are expected failures for BN_mod_exp_simple() and the internal BN_mod_exp_recp(), which will be fixed shortly.
* x509_algor: fix error messagetb2023-10-121-7/+7
|
* x509_algor: add a few missing includestb2023-10-121-1/+4
|
* x509_algor: Turn expected failure into actual failure now that the API istb2023-10-111-3/+3
| | | | fixed.
* Add preallocation dance for X509_ALGOR_set_md() as documentedtb2023-10-111-1/+5
|
* Add regress coverage for X509_ALGOR_*tb2023-10-112-2/+377
| | | | | | | | | This covers the setters and getters. Serialization and deserialization as well as comparison is already well covered by the pieces of regress using certs. There is currently one printf indicating failure. This will be fixed shortly.
* Add regress coverage for ASN1_UTCTIME_cmp_time_t()tb2023-10-051-5/+12
|
* Add some coverage for ASN1_TIME_cmp_time_t() as welltb2023-10-021-1/+14
| | | | | ASN1_UTCTIME_cmp_tim_t() could be done similarly, but then I have to mess with LIBRESSL_INTERNAL. Let's do this after unlock.
* Add regress coverage for ASN1_TIME_compare()tb2023-10-021-1/+78
|
* Minor asn1time tweakstb2023-10-021-26/+12
| | | | Sprinkle some (static) const and garbage collect an unused struct.
* Add an empty linetb2023-10-011-1/+2
|
* Allow IP addresses to be specified in a URI.beck2023-09-291-4/+50
| | | | | | | | | | | | Our checking here was a bit too aggressive, and did not permit an IP address in a URI. IP's in a URI are allowed for things like CRLdp's AIA, SAN URI's etc.). The check for this was also slightly flawed as we would permit an IP if memory allocation failed while checking for an IP. Correct both issues. ok tb@
* Appease coveritytb2023-09-291-2/+4
| | | | This is a static pointer, so it ain't ever NULL, but shrug
* Fix error messagetb2023-09-281-2/+2
|
* Don't leak ctx on failuretb2023-09-281-3/+2
|
* Add more regress coverage for EVP_CIPHER_CTX_iv_length()tb2023-09-281-1/+268
| | | | | | | Awesome: the IV length for GCM is only bounded by INT_MAX or malloc limits. In the absence of an overflowing issue tracker, I'm labeling this "good first issue", "help wanted" here.
* Check that EVP_CIPHER_CTX_iv_length() matches what was settb2023-09-281-1/+9
| | | | | | This really only covers AES-GCM. From beck
* whitespacetb2023-09-281-3/+3
|
* Fix reference to x509v3.cnf(5) bistb2023-09-261-6/+6
|
* Fix reference to x509v3.cnf(5)tb2023-09-261-6/+6
|
* Ensure no memory is leaked after passing NULL to ASN1_TIME_normalize()libressl-v3.8.1job2023-08-301-1/+4
| | | | OK tb@
* Make some global variables consttb2023-08-201-14/+15
|
* Bye bye to all people out theretb2023-08-201-28/+1
|
* Add some spaces after commatb2023-08-201-6/+6
|
* unifdef -D FULL_TESTtb2023-08-201-7/+1
|
* knfmt(1) to the rescuetb2023-08-201-139/+146
|
* Another OPENSSL_NO_DEPRECATED hits the bit buckettb2023-08-201-7/+1
|
* Drop unnecessary OPENSSL_NO_DEPRECATED dancetb2023-08-201-7/+1
|
* Use a separate flags variable for the error flags in DH_check()tb2023-08-201-7/+8
|
* Add regress coverage for ASN1_STRING_cmp()tb2023-08-151-1/+147
|
* Add some regress coverage for various ASN1_STRING types to codify sometb2023-08-151-1/+229
| | | | quirks and invariants.
* first batch of intentionally undocumented EVP constants:schwarze2023-08-121-1/+10
| | | | some EVP_MD_CTRL_*, some EVP_MD_CTX_FLAG_*, and all of EVP_F_* and EVP_R_*
* Now that the DH is sensibly called dh instead of a, we can also renametb2023-08-121-10/+10
| | | | | abuf, alen and aout to names that make sense, such as buf, buf_len and secret_len.
* a is a silly name for a DHtb2023-08-121-14/+14
|
* Use printf for consistencytb2023-08-121-5/+5
|
* Check that {DH,DSA}_get0_engine() returns NULL if OPENSSL_NO_ENGINE istb2023-08-122-2/+16
| | | | defined.
* Add regress coverage for DH and for DSA parameterstb2023-08-111-2/+267
|
* X509_STORE_CTX_get_check_issued(3) is weird.schwarze2023-08-081-0/+9
| | | | | | Both the function return type and the function name are so long that for displaying the function prototype, a line break is needed after the function return type.
* In objects.h rev. 1.17 (Jan 14, 2022),schwarze2023-08-081-7/+1
| | | | | | | | | | | | tb@ removed the following macros from the public API: _DECLARE_OBJ_BSEARCH_CMP_FN DECLARE_OBJ_BSEARCH_CMP_FN DECLARE_OBJ_BSEARCH_GLOBAL_CMP_FN IMPLEMENT_OBJ_BSEARCH_CMP_FN IMPLEMENT_OBJ_BSEARCH_GLOBAL_CMP_FN OBJ_bsearch OBJ_bsearch_ex In objects.h rev. 1.20 (Nov 11, 2022), jsing@ unifdef'ed USE_OBJ_MAC. Stop marking these names as intentionally undocumented.
* No need to mark BN_options() as intentionally undocumented any longer.schwarze2023-08-071-1/+0
| | | | | | | | In bn.h rev. 1.75 (July 31, 2023), tb@ removed it from the public API. While here, stop marking BN_prime_checks as obsolete. In BN_generate_prime.3 rev. 1.23 (May 11, 2023), tb@ documented the constant BN_prime_checks in that manual page.
* Mark asn1_ps_func as obsolete and intentionally undocumented.schwarze2023-08-071-0/+1
| | | | | In bio.h rev. 1.59 (July 28, 2023), tb@ removed the last four functions that took function pointers of this type from the public API.
* Mark BIT_STRING_BITNAME as obsolete and intentionally undocumented.schwarze2023-08-071-0/+1
| | | | | In asn1.h rev. 1.80 (July 28, 2023), tb@ removed the last three functions that were using this data type from the public API.
* Add a regress test exercising BIO_dup_chain() and triggering the leaktb2023-08-071-1/+43
| | | | fixed in bio_lib.c r1.47 as confirmed by ASAN.
* Make the bn_rand_interval() API a bit more ergonomictb2023-08-031-5/+5
| | | | | | | | | | | | | | | | | | Provide bn_rand_in_range() which is a slightly tweaked version of what was previously called bn_rand_range(). The way bn_rand_range() is called in libcrypto, the lower bound is always expressible as a word. In fact, most of the time it is 1, the DH code uses a 2, the MR tests in BPSW use 3 and an exceptinally high number appears in the Tonelli-Shanks implementation where we use 32. Converting these lower bounds to BIGNUMs on the call site is annoying so let bn_rand_interval() do that internally and route that through bn_rand_in_range(). This way we can avoid using BN_sub_word(). Adjust the bn_isqrt() test to use bn_rand_in_range() since that's the only caller that uses actual BIGNUMs as lower bounds. ok jsing
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-31 04:55:58 +0000