openbsd/src/regress/lib/libcrypto/bn, branch OPENBSD_7_4A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_42023-08-03T18:53:56+00:00Make the bn_rand_interval() API a bit more ergonomic2023-08-03T18:53:56+00:00tb2023-08-03T18:53:56+00:00urn:sha1:44ff07e01874ea8be0c72bf9d20cb7f13b76cca8
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
Retire the bn_rand_interval() test2023-08-03T18:44:31+00:00tb2023-08-03T18:44:31+00:00urn:sha1:6ce6cf23a77a446252150319206f0075eb6267cf
This test was never particularly useful. An upcoming API change for
the internal bn_rand_interval() API would require some adjustments.
It's not worth it.
Annotate bogus output as incorrect2023-07-27T06:41:39+00:00tb2023-07-27T06:41:39+00:00urn:sha1:1fff3338bb0ddbb0bc692678dddf845672732555
Some people already have way too many simple and not too important diffs in
their inbox. This isn't worth kicking something more important out of the
queue.
Add test case for negative number with highest bit of top octet set2023-07-10T20:21:37+00:00tb2023-07-10T20:21:37+00:00urn:sha1:987c9d09fa4171ebd33a66e334cf7edc8b73c437
This currently adds an incorrect 00: padding, consistent with OpenSSL's
behavior.
Add test coverage for leading zero octet dance2023-07-07T07:47:25+00:00tb2023-07-07T07:47:25+00:00urn:sha1:0ab81f6f7614b34883c7a9337251d673e142d410bn_print: remove unused bio, plug leak2023-07-06T15:11:21+00:00tb2023-07-06T15:11:21+00:00urn:sha1:83f9366821e685aefb9733e3797204f7939604adAdd regress coverage for bn_printf2023-07-06T15:08:54+00:00tb2023-07-06T15:08:54+00:00urn:sha1:f3a92efb3424a84ed8b53338aa7f8cbc8a893a9b
This must be one of the ugliest tests I've ever written, but I can't think
of a better way of doing it.
Codify BN_asc2bn(NULL, *) behavior in regress.2023-06-23T10:50:47+00:00tb2023-06-23T10:50:47+00:00urn:sha1:cd8a35403eca59025f86b12bff4b62dc923f2274Add tests for BN_sqr() corner cases.2023-06-21T07:18:10+00:00jsing2023-06-21T07:18:10+00:00urn:sha1:49d358ba4102b545829d23eeead5528ff3342df4
Test BN_sqr() with a newly allocated BN, a BN explicitly set to zero and
small values that fit in a single BN_ULONG.
Add BN_cmp()/BN_ucmp() tests with zero padded inputs.2023-06-21T07:16:08+00:00jsing2023-06-21T07:16:08+00:00urn:sha1:a88d085da8637994f920a65e914fe4811644321e
Currently BN_hex2bn() removes the leading zeros, however this will not be
the case in the future.