summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/ui/ui_null.c
diff options
context:
space:
mode:
authorjsing <>2022-12-17 15:56:25 +0000
committerjsing <>2022-12-17 15:56:25 +0000
commit8cb0d6719a25ad287afaef9db9c434e2ffbe86a7 (patch)
treedebf6c87cb5650b9a030d3c9de7f062c9bce2cd7 /src/lib/libcrypto/ui/ui_null.c
parent4f30e7935ccf9f6d7cff0669aecfdf86fd5b2d9d (diff)
downloadopenbsd-8cb0d6719a25ad287afaef9db9c434e2ffbe86a7.tar.gz
openbsd-8cb0d6719a25ad287afaef9db9c434e2ffbe86a7.tar.bz2
openbsd-8cb0d6719a25ad287afaef9db9c434e2ffbe86a7.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/ui_null.c')
0 files changed, 0 insertions, 0 deletions