summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/recallocarray.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-04-07bn_test: drop a few braces that are now unnecessarytb1-33/+17
2023-04-07bn_test: move rc initialization to its own linetb1-9/+17
2023-04-07bn_test: keep the error stack cleantb1-1/+13
Make message() print and clear the error stack. This way we can know what test errored. To make this work also clear the error stack after a handful of xfail tests.
2023-04-07bn_test: use bn_copy() instead of BN_free/BN_duptb1-3/+2
This is not only simpler but also required by an upcoming change.
2023-04-07bn_test: a few early return would leak. goto err insteadtb1-5/+5
2023-04-07bn_test: rand_neg() is not only one of the most stupidly named functionstb1-2/+2
in the entire code base it also has a few parentheses too many
2023-04-07bn_test: handle rc consistentlytb1-111/+134
Various test functions had bugs due to the fact that the return code would be set to 1 at the top so that each error would have to set rc = 0. This is silly. Fail closed instead by setting rc = 0 at the top and only flipping to 1 before the err label
2023-04-07bn_test: inline the only use of lst[]tb1-14/+12
lst[] can be converted from a bit string to a hex string. Use BN_hex2bn() isntead of BN_bin2bn(). Handle this inside test_lshift() rather than doing artistic ownership dances.
2023-04-07Improve some test failure reportingtb1-5/+12
2023-04-07Ignore ten getter and setter control macros related to proxy BIOs.schwarze1-0/+6
Those are not useful because such a BIO type neither exists in LibreSSL nor in OpenSSL 1.1.1. Not adding the deprecation notice to some manual page because there is no manual page that is even vaguely related.
2023-04-07Two minor tweaks that are useful for processing bio.h, among other headers:schwarze1-1/+2
* ignore lines defining "__bounded__()" * ignore whitespace between "#" and "include"
2023-04-07Mark BIO_CB_return(), BIO_cb_pre(), and BIO_cb_post() as intentionallyschwarze1-2/+7
undocumented because they are unused according to codesearch.debian.net and would cause nothing but obfuscation if they were used.
2023-04-06Document the effects that BIO_set_info_callback(3), BIO_callback_ctrl(3),schwarze1-3/+54
BIO_get_info_callback(3), and BIO_info_cb(3) have on connect BIOs.
2023-04-06Properly document BIO_set_info_callback(3) and BIO_get_info_callback(3)schwarze1-8/+96
which where mentioned below SYNOPSIS and HISTORY but not described. Also document the command constant BIO_CTRL_SET_CALLBACK and the deprecated function type name bio_info_cb(3). Mention that callbacks installed using BIO_set_callback_ex(3) and BIO_set_callback(3) can tamper with *all* the return values.
2023-04-06Use RCS tag instead of an incorrect path.tb1-1/+1
2023-04-06Move a comment to the proper placetb1-6/+5
2023-04-06wycheproof: fix copy-paste error in previoustb1-2/+2
2023-04-06wycheproof: use EVP_MD instead of importing "hash"tb1-70/+52
2023-04-06Check and assign on one linetb1-3/+2
2023-04-06Zap extra empty linetb1-2/+1
2023-04-05Add a few missing bracestb1-4/+7
ok jsing
2023-04-05Set up the RSA's _method_mod_n before the initial blindingtb1-11/+13
As observed by Bernd Edlinger, the main part of the RSA timing leak that was recently made public is that the initial blinding isn't done with Montgomery exponentiation but rather with plain exponentiation. Pull up the initialization of the cached Montgomery context to ensure we use Montgomery exponentiation. Do this for private_{de,en}crypt(). Interestingly, the latter was fixed in OpenSSL a while ago by Andy Polyakov as part of the "smooth CRT-RSA" addition. If this code was anything but completely insane this would never have been an issue in the first place. But it's libcrypto... ok jsing
2023-04-05Sprinkle a few BTI instructions into the arm64 assembly files and passkettenis2-1/+8
-mmark-bti-property to indicate those now have BTI support. ok jsing@, deraadt@
2023-04-05bn_mod_sqrt: Improve a handful of comments and a printftb1-5/+9
2023-04-05Improve regress coverage for BN_mod_sqrt()tb1-3/+2783
This now covers all the main branches of both the old and new BN_mod_sqrt() implementation except for negative p.
2023-04-05Simplify mod_sqrt_test() a bittb1-35/+16
2023-04-05bn_mod_sqrt test: Use a #define rather than hard coded 100tb1-3/+5
2023-04-05Add coverage for the truly non-deterministic path of Tonelli-Shankstb1-4/+1625
Regress coverage of all of BN_mod_sqrt() is still lacking after this. This will improve in forthcoming commits.
2023-04-05Introduce variation in location of junked bytes; ok tb@otto1-3/+8
2023-04-04A refactoring back in 2016 in which magic numbers where extracted intoanton1-0/+1
named constants accidentally dropped an instruction causing detection of eXtended operations (XOP) on AMD hardware to break. ok miod@ tb@
2023-04-04In preparation for better documenting BIO info callbacks, improve theschwarze1-9/+115
description of BIO_ctrl(3) and its three siblings. Given the vast range of effects these functions can have, the text is unavoidably still vague, but at least some information can be provided. While here, fix one wrong parameter type and three inconsistent parameter names in the SYNOPSIS.
2023-04-04Clean bn_mod_sqrt up a littletb1-28/+53
This makes it look a bit more like other tests and also prepares the addition of further test cases and different tests.
2023-04-03Compress euclid() a littletb1-49/+28
This function is spread out over way too many lines and has too much repetition. Once this is made a little more compact, it becomes clearer that this is a somewhat obfuscated version of binary gcd (it is not constant time therefore cryptographically unsound. It is not used internally). This will likely go away later. ok jsing
2023-04-03Link bn_gcd test to regresstb1-1/+3