| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Remove dangling references to BN_get0_nist_prime_521(3) | tb | 2023-04-27 | 1 | -6/+4 |
| | | |||||
| * | In the next major bump, some BN macros will become functions. | schwarze | 2021-12-06 | 1 | -7/+2 |
| | | | | | | | 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 | jsg | 2021-03-12 | 1 | -3/+3 |
| | | |||||
| * | In view of the recent BN_FLG_CONSTTIME vulnerabilities in OpenSSL, | schwarze | 2018-04-29 | 1 | -21/+38 |
| | | | | | | | | | | | | | | | | | 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 | schwarze | 2018-03-21 | 1 | -2/+8 |
| | | |||||
| * | Document BN_set_flags(3) and BN_get_flags(3). | schwarze | 2017-01-30 | 1 | -0/+144 |
| jsing@ confirmed that these macros are public and worth documenting. | |||||
 |
index : openbsd | |
| A mirror of https://github.com/libressl/openbsd.git |
| summaryrefslogtreecommitdiff |