summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Rename OBJ_add_sigid.3 to OBJ_find_sigid_algs.3tb2023-07-222-92/+2
|
* bio_asn1 tests: drop unneeded variabletb2023-07-211-3/+2
|
* Add missing license for rsa_local.htb2023-07-211-1/+57
| | | | discussed with jsing
* Simple adjustments for DSO removaltb2023-07-212-8/+6
| | | | openssl.cnf.5 will need a major overhaul. But that isn't new...
* Stop mentioning some ERR_load_*_strings that will be removedtb2023-07-211-6/+2
|
* Provide a bunch of always failing ENGINE APItb2023-07-213-6/+166
| | | | | | | | | | | | | | | This commit adds a few symbols under OPENSSL_NO_ENGINE. They will be used after the main ENGINE code is disabled in the next bump. The ecosystem is mostly prepared for dealing with a libcrypto compiled with OPENSSL_NO_ENGINE. There are a few stragglers like M2Crypto, dovecot and the latest apr-util release (fixed in their development branch). To avoid intrusive patching in these ports, we need to keep a bunch of ENGINE symbols around despite adding OPENSSL_NO_ENGINE. This of course meant patching some other ports, but that was way easier. ok jsing
* Fix Xr order to appease mandoc -Tlinttb2023-07-211-4/+4
|
* Remove OBJ_add_sigid and OBJ_sigid_free documentationtb2023-07-215-54/+14
| | | | | These will be made internal and will likely go away. The OBJ_add_sigid.3 manual should probably be renamed; this can be done in a second step.
* Remove ASN1_buf_print documentationtb2023-07-213-74/+3
| | | | This function will be made internal-only and likely be renamed/rewritten.
* Remove remaining ECDSA_METHOD documentationtb2023-07-211-29/+4
|
* Remove documentation of ECDH/ECDSA ex_data APItb2023-07-211-21/+3
|
* Document ENGINE_get_default_ECtb2023-07-211-17/+8
| | | | | | | ENGINE_get_default_{ECDH,ECDSA} will go away and won't come back. Replace their documentation with the missing ENGINE_get_defaulT_EC. In the unlikely event that we will need to bring back ENGINE after the next bump, this manual will not be outdated and incomplete.
* Document ENGINE_{get,set}_ECtb2023-07-211-29/+17
| | | | | | | ENGINE_{get,set}_{ECDH,ECDSA} will go away and won't come back. Replace their documentation with the missing ENGINE_{get,set}_EC. In the unlikely event that we will need to bring back ENGINE after the next bump, this manual will not be outdated and incomplete.
* Remove a few workarounds that are no longer necessarytb2023-07-201-4/+1
|
* Remove some ancient cruft that hasn't been used in agestb2023-07-204-1695/+1
| | | | discussed with jsing
* Move get_rfc3526_prime_8192.3 to BN_get_rfc3526_prime_8192.3tb2023-07-202-4/+4
| | | | | This way we will have a manual corresponding to an existing function after the next bump.
* Remove unnecessary inclusion of dso.htb2023-07-203-6/+3
|
* Remove last internal consumer of DSOtb2023-07-201-80/+9
| | | | | | | | | | | | It is currently possible to extend libcrypto by having it load a shared object via dlopen() either from a config file on library initialization or when an application calls the relevant API. Recent and not so recent events showed how dangerous an idea dlopen() is. Independently of such concerns, this should not be handled in the characteristically convoluted way of this toolkit. DSO will go away in the upcoming bump. This commit clears the road for a plain cvs rm of the dso code. ok jsing
* eng_aesni.c: add evp_local.h so it compiles again.tb2023-07-201-1/+3
|
* Remove get_rfc*_prime_* documentationtb2023-07-202-46/+20
| | | | | | Their BN_get_rfc*_prime_* aliases from the OpenSSL 1.1 API will remain. Perhaps the manual should be moved to BN_get_rfc3526_prime_8192.3; that can be done in a second step.
* Remove ECDSA_{do_,}sign_ex() and ECDSA_sign_setup()tb2023-07-204-103/+20
| | | | | These very poorly designed interfaces will go away, so stop documenting them.
* Cap the size of numbers we check for primalitytb2023-07-201-1/+12
| | | | | | | | | | | We refuse to generate RSA keys larger than 16k and DH keys larger than 10k. Primality checking with adversarial input is a DoS vector, so simply don't do this. Introduce a cap of 32k for numbers we try to test for primality, which should be more than large enough for use withing a non-toolkit crypto library. This is one way of mitigating the DH_check()/EVP_PKEY_param_check() issue. ok jsing miod
* Don't rely on the libssl headers pulling in stdio.h somehowtb2023-07-191-1/+3
|
* Add missing commas to test vectorsjoshua2023-07-191-26/+26
| | | | ok tb@
* Add test coverage for SHA3joshua2023-07-191-27/+344
| | | | ok tb@
* Fix two aliases in libcrypto spotted by the new symbols testtb2023-07-192-3/+4
| | | | ok jsing
* ecc_cdh: plug leak of peer public keytb2023-07-161-1/+2
|
* ecdhtest: Drop unnecessary constant and unneeded includestb2023-07-161-10/+6
|
* ecdhtest: fix a couple bugs plus some cosmetic tweakstb2023-07-161-6/+6
|
* fix include directive - this is make, not Ctb2023-07-151-2/+2
|
* Rework the ecdhtesttb2023-07-151-260/+252
| | | | | | | | | Test keyshare for all built-in curves and simplify, especially printing on failure. Incorporate known answer tests from RFC 5114 and RFC 5903. All in all, this is a lot less code and a lot more test coverage and hopefully a little less eyebleed. Very loosely based on OpenSSL b438f0ed by Billy Brumley
* Fix return value check for ECDH_compute_key()tb2023-07-151-5/+5
| | | | | | ECDH_compute_key() usually returns -1 on error (but sometimes 0). This was also the case in OpenSSL when these tests were written. This will soon change. The check for <= 0 will still be correct.
* Add test coverage for cofactor ECDH using NIST test vectorstb2023-07-152-2/+2509
| | | | | | | | | Since all non-binary NIST curves have cofactor 1, this is in effect plain ECDH. Current regress coverage of ECDH is quite lacking on architectures where Go isn't available. This fixes that. Actual cofactor ECDH support may be added soon to libcrypto, at which point I will also add testcases with cofactor > 1.
* Link symbols test to buildtb2023-07-151-1/+2
|
* remove accidentally imported files againtb2023-07-153-2713/+0
|
* Import a version of libcrypto's symbols test for libssltb2023-07-155-0/+2798
|
* Mop up MD32_XARRAY from md5.jsing2023-07-151-91/+84
| | | | | | | MD32_XARRAY was added as a workaround for a broken HP C compiler (circa 1999). Clean it up to simplify the code. No change in generated assembly.
* Mop up MD32_XARRAY from md4.jsing2023-07-151-75/+68
| | | | | | | MD32_XARRAY was added as a workaround for a broken HP C compiler (circa 1999). Clean it up to simplify the code. No change in generated assembly.
* Refactor ASN1_item_sign_ctx()tb2023-07-131-54/+89
| | | | | | | | | | | | | | | | | | | | | | Oh, joy! The muppets had a feast: they could combine the horrors of EVP with X.509... Return values between -1 and 3 indicating how much work needs to be done, depending on whether methods are present or absent. Needless to say that RSA and EdDSA had inconsistent return values until recently. Instead of interleaving if/else branches, split out two helper functions that do essentially independent things, which results in something that isn't entirely bad. Well, at least not compared to the surrounding code. asn1_item_set_algorithm_identifiers() extracts the signature algorithm from the digest and pkey if known, and sets it on the two X509_ALGOR that may or may not have been passed in. asn1_item_sign() converts data into der and signs. Of course there were also a few leaks and missing error checks. ok jsing
* Revert accidental addition of cofactor ECDH supporttb2023-07-121-16/+2
| | | | This snuck in with ech_key.c r1.33 because I committed from a dirty tree.
* Reenable clienttest and servertesttb2023-07-121-3/+3
|
* Fix last bit of the clienttest, needs ssl_pkt.c r1.66tb2023-07-111-2/+2
|
* Remove old workaround for F5tb2023-07-111-13/+2
| | | | | | | | | | | F5 is well-known for needing workaround (go read RFC 8446). In this particular case, it required implementation sending CHs larger than 255 bytes to 0x0300 otherwise their server would hang. This is the same hang that required the CH padding extension which broke other implementations. The CH padding extension was removed ~6 years ago, so hopefully this kludge will no longer needed either. ok jsing
* Keep servertest silent and align with clienttesttb2023-07-111-2/+3
|
* Neuter expected server test failures with SSLv2tb2023-07-111-1/+6
| | | | This test should either be extended or retired. As it is it is useless.
* Fix most of the clienttest. With this only test cases 9 and 13 fail.tb2023-07-111-23/+39
|
* Add test case for negative number with highest bit of top octet settb2023-07-101-1/+13
| | | | | This currently adds an incorrect 00: padding, consistent with OpenSSL's behavior.
* Rename EC_KEY from r to key like in the rest of the filetb2023-07-101-4/+4
|
* Pull BIGNUM constants out of get_* function bodiestb2023-07-101-315/+331
| | | | | | | | | The get_rfc*_prime_* functions will be removed. The constants will remain for the BN_get_rfc*_prime_* functions. Make the latter call BN_bin2bn() directly on these constants rather than going through get_*. This avoids some overlong lines. Also KNF for some comments. Reduces the diff I currently carry by quite a bit.
* BIO_indent: use %*s rather than puts in a looptb2023-07-101-6/+5
| | | | ok beck jsing millert
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-03 11:50:29 +0000