summaryrefslogtreecommitdiff
path: root/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ectest: drop a broken #if 0 /* optional */ piece of codetb2023-04-181-20/+5
| | | | | This places a point at infinity and then fails. Fix some wacky indentation in the vicinity.
* ec_point_conversion: drop test for sect571k1tb2023-04-181-350/+2
| | | | Maybe it should be replaced by another test, although P-256 seems enough.
* ectest: drop some gross unused macrostb2023-04-181-49/+1
|
* ectest: unifdef OPENSSL_NO_EC2Mtb2023-04-181-418/+1
|
* Skip binary curves in ec_point_conversiontb2023-04-171-3/+14
|
* Switch all ec tests to using dynamic linkingtb2023-04-173-8/+14
| | | | | This only requires very minor changes and simplifies testing quite a bit. Some of the changes can be undone after the next bump.
* Simplify Makefiletb2023-04-171-12/+1
|
* Drop GF2m teststb2023-04-171-647/+1
| | | | The code they test will go away soon.
* Allow overriding the bc implementation used in run-bctb2023-04-171-2/+7
| | | | | | | | | | | | While base bc is great, it uses libcrypto's BIGNUM implementation. This implies that the independent verification of the bn_test isn't as independent as it should be. With this commit, run-bc picks up bn-gh if it is installed. This appears to work on amd64, arm64 and sparc64 (where gbc is busted). I will send PRs to the regress maintainers once I will have tested this a bit more thoroughly. Committing this early since I juggle way too many diffs already.
* Fix typotb2023-04-171-2/+2
|
* Drop two useless READMEstb2023-04-172-18/+0
| | | | "go ahead" jsing
* Skip sect* curve checkstb2023-04-171-2/+2
| | | | | GF2m curves will go away soon. This reduces the pile of diffs in my jungle a tiny little bit.
* c_zlib.c needs bio_local.h with -DZLIB.tb2023-04-171-1/+2
| | | | | Apparently nobody tried to compile libcrypto with ZLI since Jan 2022. Maybe this means that we can unifdef -U ZLIB or maybe not...
* Tweak indent and use named registers.jsing2023-04-171-13/+13
| | | | No functional change.
* Hook sha3 up to build.jsing2023-04-171-1/+3
| | | | ok tb@
* Move BN_bn2mpi()/BN_mpi2bn() into bn_convert.cjsing2023-04-173-138/+74
|
* Use C99 initializers for the default_pctx and mark it static consttb2023-04-171-8/+3
|
* Add missing const qualifiers to the v3_* externstb2023-04-171-11/+11
| | | | ok jsing
* Fix whitespace in DHparam_print_fp()tb2023-04-171-2/+4
|
* Remove now unused dh_prn.ctb2023-04-171-64/+0
|
* Drop dh_prn.ctb2023-04-171-2/+1
|
* Move DHparam_print_fp() next to DHparam_print()tb2023-04-172-17/+18
| | | | | As usual with the fp suffix, the former wraps the latter with a file BIO. There is no reason for this function to be in a separate file.
* remove bad Pp;jmc2023-04-171-3/+2
| | | | (sorry, otto, for not spotting in the updated diff)
* Fix previous: add a missing andtb2023-04-161-2/+3
|
* Dump (leak) info using utrace(2) and compile the code always inotto2023-04-162-148/+199
| | | | | except for bootblocks. This way we have built-in leak detecction always (if enable by malloc flags). See man pages for details.
* Garbage collect the now unused obfuscating macro string_stack_free()tb2023-04-161-4/+1
|
* Inline the three uses of string_stack_free()tb2023-04-161-4/+4
| | | | | | | sk_OPENSSL_STRING_pop_free() is much more explicit and isn't that much more complicated. x509_util.c can also use it directly... No binary change
* Remove the now unused vpm_int.htb2023-04-161-64/+0
|
* x509_vfy.c and x509_vpm.c don't need vpm_int.h anymoretb2023-04-162-4/+4
|
* Move X509_VERIFY_PARAM_st from vpm_int.h to x509_local.htb2023-04-162-13/+13
|
* Provide EVP methods for SHA3 224/256/384/512.jsing2023-04-163-2/+193
| | | | ok tb@
* Provide EVP methods for SHA512/224 and SHA512/256.jsing2023-04-164-4/+91
| | | | ok tb@
* Bounds check mdlen that is passed to sha3_init().jsing2023-04-161-2/+5
| | | | While here, use KECCAK_BYTE_WIDTH instead of hardcoding the value.
* Shuffle ext_cmp() and ext_list_free() up a bittb2023-04-161-18/+14
|
* Remove unnecessary prototypes in the middle of the codetb2023-04-161-5/+1
| | | | In addition, ext_cmp() was already prototyped earlier...
* Use more usual version of inlined nitems(). No binary change.tb2023-04-161-2/+2
|
* Fix comment formatting and grammar, drop usless and outdated commenttb2023-04-161-7/+3
|
* Remove now empty/unused ext_dat.htb2023-04-161-67/+0
|
* Merge ext_dat.h back into x509_lib.ctb2023-04-162-78/+78
| | | | | | There is no point in having this in a separate internal header. discussed with jsing
* Mark X9.31 BN API for removaltb2023-04-161-1/+4
| | | | | | | This supports a mostly forgotten, seemingly unused and long retired standard. No need for this in our public API Dyson sphere. ok jsing
* The BN reciprocal API will also become internal-onlytb2023-04-161-1/+7
| | | | | | | This is unused outside of the library and could do with some reworking. That's easier without having to care about outside consumers. ok jsing
* Various BN*init() will be removed from the public APItb2023-04-161-1/+10
| | | | | | | | With the corresponding structs now being opaque, the only thing they are good for outside the library are memory leaks. They will be removed completely or become internal only. ok jsing
* Mark public bn_nist and ec_nist API for removaltb2023-04-162-2/+6
| | | | | | | | | | | | | The faster nist code is rife with problematic C. While this is generally considered to be a pleonasm nowadays, here it specifically refers to aliasing issues and other flavors of undefined behavior. With compilers and standardization committees becoming seemingly more determined about making C even more unusable than it already is, this code has resulted in miscompilations and generally is a target rich environment for fuzzers to feast on. We're better off without it. Go look while it's still there. It's some of the very worst we have to offer. ok jsing
* Mark EC_KEY_{get,insert}_method_data() for removaltb2023-04-161-1/+5
| | | | | | | This is unused and in the way of some house keeping. Thus it will be relocated to the attic. ok jsing
* Mark TS_VERIFY_CTX_init() for removaltb2023-04-161-1/+3
| | | | | | | With opaque TS_VERIFY_CTX the init function dangerous and useless. It will be dropped. ok jsing
* Prepare addition of X509_STORE_CTX_get1_{certs,crls}(3)tb2023-04-162-2/+27
| | | | | | | | | | | | | | | X509_STORE_get1_{certs,crls}(3) was added to the OpenSSL 1.1 API with the usual care. At some point later it was noticed that they didn't deal with an X509_STORE at all, but rather with an X509_STORE_CTX, so were misnamed. The fact that X509_STORE_CTX and X509_STORE have their roles reversed when compared to other FOO vs FOO_CTX in this API may or may not be related. Anyway, the X509_STORE versions will be demoted to compat defines and the X509_STORE_CTX will be added to match OpenSSL 1.1 API more closely. This was pointed out by schwarze a long time ago and missed in a few bumps. Hopefully we'll manage to do it this time around. ok jsing
* Mark remaining policy tree public API for removaltb2023-04-162-3/+19
| | | | ok jsing
* Annotate policy tree STACK_OF() goo for removal from public APItb2023-04-161-1/+4
| | | | ok jsing
* The policy tree types become internal ony. Annotate them.tb2023-04-161-1/+7
| | | | ok jsing
* Cipher text stealing will go away. Mark it for removal.tb2023-04-161-1/+3
| | | | ok jsing
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-27 21:19:19 +0000