openbsd/src/lib/libcrypto/man/BN_set_flags.3, branch OPENBSD_7_9_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2025-06-08T22:40:31+00:00 .Lb libcrypto ; OK tb@ 2025-06-08T22:40:31+00:00 schwarze 2025-06-08T22:40:31+00:00 urn:sha1:8be86af02fed1bda350c8dd14ee064cb66e3b0f5 Remove dangling references to BN_get0_nist_prime_521(3) 2023-04-27T07:22:22+00:00 tb 2023-04-27T07:22:22+00:00 urn:sha1:6eccb6752ebbd41e92f467cf0b542b7524b47893 In the next major bump, some BN macros will become functions. 2021-12-06T19:45:27+00:00 schwarze 2021-12-06T19:45:27+00:00 urn:sha1:036164e800dded700d72e343b440ebe3a04af264 In order to not forget it, already remove the statements that these APIs are currently implemented as macros: Not saying that doesn't make the documentation wrong. spelling 2021-03-12T05:18:00+00:00 jsg 2021-03-12T05:18:00+00:00 urn:sha1:ec8ac30cd58ba3d7f8f88c981b5996b33c1f72f7 In view of the recent BN_FLG_CONSTTIME vulnerabilities in OpenSSL, 2018-04-29T15:58:21+00:00 schwarze 2018-04-29T15:58:21+00:00 urn:sha1:0cafa356a8c4c7fcd0ceea551f687c5d7fbef24e carefully document constant time vs. non-constant time operation of BN_div(3), BN_mod_exp(3), and BN_mod_inverse(3). Until the work that is required on the ill-designed BN_exp(3) and BN_gcd(3) interfaces can be undertaken, also document the imperfections in their behaviour, for now. Finally, mention BN_mod_exp(3) behaviour for even moduli. Delete the vague statement about some functions automatically setting BN_FLG_CONSTTIME. It created a false sense of security. Do not rely on it: not all relevant functions do that. Topic brought up by beck@, significant feedback and OK jsing@. crypto HISTORY up to SSLeay 0.9.1; researched from OpenSSL git 2018-03-21T09:03:49+00:00 schwarze 2018-03-21T09:03:49+00:00 urn:sha1:9c6b7656d1237ca414073bcf0955561c2e9e90cc Document BN_set_flags(3) and BN_get_flags(3). 2017-01-30T01:29:31+00:00 schwarze 2017-01-30T01:29:31+00:00 urn:sha1:19dcc2c9146afbb7e7ee92dd56ef7f469c46c87e jsing@ confirmed that these macros are public and worth documenting.