summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/BN_mod_inverse.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* In view of the recent BN_FLG_CONSTTIME vulnerabilities in OpenSSL,schwarze2018-04-291-2/+10
| | | | | | | | | | | | | | | | 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@.
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-271-3/+3
| | | | on the web, so fix up SSLeay HISTORY accordingly
* crypto HISTORY up to SSLeay 0.9.1; researched from OpenSSL gitschwarze2018-03-211-2/+7
|
* bn.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-201-3/+4
|
* Document BN_set_flags(3) and BN_get_flags(3).schwarze2017-01-301-3/+3
| | | | jsing@ confirmed that these macros are public and worth documenting.
* replace all references to bn(3) with BN_new(3),schwarze2016-12-101-3/+3
| | | | and make sure all BN*(3) pages point back to BN_new(3)
* Copyright and licenseschwarze2016-11-201-2/+50
|
* some cleanup;jmc2016-11-081-3/+3
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* fourth batch of perlpod(1) to mdoc(7) conversionschwarze2015-02-231-0/+59