| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@.
|
|
|
|
| |
on the web, so fix up SSLeay HISTORY accordingly
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
jsing@ confirmed that these macros are public and worth documenting.
|
| |
|
|
|
|
| |
and make sure all BN*(3) pages point back to BN_new(3)
|
|
|
|
|
| |
Merge a sentence from OpenSSL saying that BN_sub(3)
can do in-place manipulation.
|
| |
|
|
|
|
| |
feedback and OK bcook@, OK jsing@
|
|
|