diff options
author | jsing <> | 2022-12-17 15:56:25 +0000 |
---|---|---|
committer | jsing <> | 2022-12-17 15:56:25 +0000 |
commit | a9f292ba0c26c0212f3cee4f53591dbdec7ee05c (patch) | |
tree | debf6c87cb5650b9a030d3c9de7f062c9bce2cd7 /src/lib/libcrypto/ui | |
parent | 1dd1001dfe28a3e1f6775d022a3d5be252da4459 (diff) | |
download | openbsd-a9f292ba0c26c0212f3cee4f53591dbdec7ee05c.tar.gz openbsd-a9f292ba0c26c0212f3cee4f53591dbdec7ee05c.tar.bz2 openbsd-a9f292ba0c26c0212f3cee4f53591dbdec7ee05c.zip |
Provide BN_zero()/BN_one() as functions and make BN_zero() always succeed.
BN_zero() is currently implemented using BN_set_word(), which means it can
fail, however almost nothing ever checks the return value. A long time
ago OpenSSL changed BN_zero() to always succeed and return void, however
kept BN_zero as a macro that calls a new BN_zero_ex() function, so that
it can be switched back to the "can fail" version.
Take a simpler approach - change BN_zero()/BN_one() to functions and make
BN_zero() always succeed. This will be exposed in the next bump, at which
point we can hopefully also remove the BN_zero_ex() function.
ok tb@
Diffstat (limited to 'src/lib/libcrypto/ui')
0 files changed, 0 insertions, 0 deletions