summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/BN_add.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* One more reciprocal thing hid in here (yay for consistent naming)tb2023-04-271-2/+1
|
* Remove stale references to BN reciprocal stufftb2023-04-271-6/+4
|
* Correctly detect b < a in BN_usub().jsing2023-01-311-4/+3
| | | | | | | | | | | | BN_usub() requires that a >= b and should return an error in the case that b < a. This is currently only detected by checking the number of words in a versus b - if they have the same number of words, the top word is not checked and b < a, which then succeeds and produces an incorrect result. Fix this by checking for the case where a and b have an equal number of words, yet there is a borrow returned from bn_sub_words(). ok miod@ tb@
* Mark BN_mod_exp2_mont() as intentionally undocumented.schwarze2022-11-161-3/+4
| | | | | | | | | | | It appears to be intended for internal use by DSA_do_verify(3) and using codesearch.debian.net, i found nothing outside OpenSSL/LibreSSL using it. In April 2018, jsing@ questioned whether the five related functions BN_mod_exp_mont() and friends should even be exposed by <openssl/bn.h>, so we decided to not document them. Now tb@ agrees that there is no reason to document BN_mod_exp2_mont() as long as we don't want to document BN_mod_exp_mont().
* document BN_mod_add_quick(3), BN_mod_sub_quick(3), BN_mod_lshift(3),schwarze2021-12-201-3/+115
| | | | BN_mod_lshift_quick(3), BN_mod_lshift1(3), and BN_mod_lshift1_quick(3)
* document BN_uadd(3) and BN_usub(3)schwarze2021-12-191-7/+78
|
* Add missing const qualifiers in a number of BN_* manuals.tb2021-11-301-17/+17
| | | | ok schwarze
* In view of the recent BN_FLG_CONSTTIME vulnerabilities in OpenSSL,schwarze2018-04-291-2/+49
| | | | | | | | | | | | | | | | 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 0.9.7; researched from OpenSSL gitschwarze2018-03-221-3/+4
|
* crypto HISTORY up to SSLeay 0.9.1; researched from OpenSSL gitschwarze2018-03-211-2/+4
|
* bn.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL gitschwarze2018-03-211-5/+6
|
* bn.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-201-3/+6
|
* Document BN_set_flags(3) and BN_get_flags(3).schwarze2017-01-301-4/+4
| | | | jsing@ confirmed that these macros are public and worth documenting.
* correctly mark all documented macros found in <openssl/bn.h>schwarze2017-01-071-2/+3
|
* 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)
* Add Copyright and license.schwarze2016-11-201-2/+58
| | | | | Merge a sentence from OpenSSL saying that BN_sub(3) can do in-place manipulation.
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* document BN_set_negative() and BN_is_negative();schwarze2016-11-051-1/+2
| | | | feedback and OK bcook@, OK jsing@
* fourth batch of perlpod(1) to mdoc(7) conversionschwarze2015-02-231-0/+352
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-26 12:36:10 +0000