summaryrefslogtreecommitdiff
path: root/src/regress/lib/libcrypto/ec (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ec_asn1_test: Prepare for upcoming bumptb9 days2-8/+11
| | | | | Linking statically, pull in ec_local.h and provide a prototype for EC_GROUP_new(), which will be removed from the public API.
* Remove pointless call to EC_GROUP_precompute_mul()tb2025-01-241-3/+1
|
* ectest: zap stray whitespacetb2025-01-221-2/+2
|
* ectest: fix misleading indentationtb2025-01-221-5/+7
|
* ectest: remove unused definestb2025-01-221-5/+1
|
* ectest: even more lipsticktb2025-01-221-17/+15
|
* ectest: apply some more lipsticktb2025-01-221-8/+3
|
* ectest: switch from new + copy to dup. zap some NULL checks before freetb2025-01-221-42/+15
|
* Ensure the cyclic subgroup cycles in the expected number of iterations.jsing2025-01-221-9/+14
| | | | Also print the iteration number and fix some indentation.
* ectest: heed long forgotten XXX and switch back to BN_one()tb2025-01-221-3/+2
|
* ec/Makefile: remove excess tabstb2025-01-211-9/+9
|
* An -> Thetb2025-01-061-2/+2
| | | | | There's only one inverse and in standard affine coordinates it only has one representation.
* Print the inverse in affine coordinatestb2025-01-061-8/+3
| | | | | This way we can get rid of the stupidity that is publicly exposed Jprojective coordinates soon.
* Remove already disabled tests for elliptic curves of small ordertb2024-12-241-642/+1
|
* Disable regression tests for small builtin curvestb2024-11-241-1/+7
|
* ec_asn1_test: remove extra parenstb2024-11-081-4/+4
|
* ec_asn1_test: remove debug leftover that broke the build on Windowstb2024-11-051-3/+1
|
* ec tests: allow linking against eopenssltb2024-11-042-3/+16
|
* ec_asn1_test: I somehow managed to commit the version without freezero...tb2024-11-021-3/+4
|
* ec_asn1_test: set compressed coordinates for the "simple" generatortb2024-11-011-3/+3
|
* Also exercise the "simple" version of the builtin curves, not only "mont"tb2024-11-011-27/+124
|
* Split ec_key_test_point_encoding() into chunks of saner sizetb2024-10-291-49/+172
|
* ec_asn1_test: point doubling is fine, the leak is elsewheretb2024-10-291-3/+1
| | | | (will be fixed shortly).
* Disable point doubling for now, it leaks due to a doc bug.tb2024-10-291-1/+3
| | | | | Can't replace it with adding the point to itself since that also leaks (another doc bug). Who would've thought.
* unifdef -m -DCORRECT_PRIV_KEY_PADDING=1 ec_asn1_test.ctb2024-10-281-9/+1
|
* Enable the tests that depend on correct private key paddingtb2024-10-281-2/+2
|
* {d2i,i2d}_ECParameters() also want a bit of exercisingtb2024-10-261-1/+28
|
* ec_asn1_test: play some silly games to cover a few more code pathstb2024-10-261-1/+47
|
* Add regress coverage for ec_print.ctb2024-10-261-2/+889
| | | | | | | | | | | | | | | | | Of course the four stunning beauties in there aren't printing anything. the hex family converts an elliptic curve point's X9.62 encoding into a hex string (which kind of makes sense, you can print that if you want). Much more astounding is EC_POINT_point2bn() where the X9.62 octet string is interpreted as a BIGNUM. Yes, the bignum's hex digits are the point conversion form followed by the affine coordinate(s) of the elliptic curve point, and yes you can choose between compressed, uncompressed, and hybrid encoding, why do you ask? This doesn't really make any sense whatsoever but of course you can also print that if you really want to. Of course the beloved platinum members of the "gotta try every terrible OpenSSL interface" club had to use and expose this.
* Use macros describing the intent rather than #if 0tb2024-10-251-8/+38
|
* Add regress for {d2i,i2d}_ECPrivateKey() and {o2i,i2o}_ECPublicKey()tb2024-10-251-1/+1003
| | | | Some test cases are disabled since they exercise an upcoming bug fix.
* ec_point_conversion: cosmeticstb2024-10-231-4/+4
|
* ec_point_conversion: extend test coverage by translating back thetb2024-10-231-2/+76
| | | | | | point to an octet string and match with the initial octet string. would have caught the regression found by anton
* ec_asn1_test: simplify previoustb2024-10-181-7/+4
|
* ec_asn1_test: call EC_GROUP_check() for the builtin curvestb2024-10-182-59/+13
| | | | | This makes the internal curve test in ectest.c superfluous. Also fix a logic error.
* ec_asn1_test: adjust for rejection of non-builtin curve parameterstb2024-10-181-14/+2
|
* ec_asn1_test: add secp256k1.mtb2024-10-181-10/+81
|
* ec_asn1_test: remove last hardcoded wei25519 remnanttb2024-10-181-4/+3
|
* ec_asn1_test: test Wei25519.2 and Wei25519.-3 as welltb2024-10-181-37/+163
| | | | Covers a few more corner cases in the elliptic curve code.
* ec_asn1_test: clean up & refactor; test Wei25519 with simple methodtb2024-10-181-109/+189
|
* EC ASN.1: add reminder that the simple method might also want testingtb2024-10-161-1/+5
|
* Implement Wei25519 to exercise some more elliptic curve codetb2024-10-161-1/+284
| | | | | | | | This provides a non-trivial non-builtin curve that is unlikely to ever become a builtin curve. This exercises the cofactor guessing code and and ensures that things work as far as they can with a custom OID. The main reason for adding it is to have a "real-world" example for an upcoming check that EC parameters represent a builtin curve.
* Extend ec_asn1_test to check for correct curve coefficient encodingtb2024-10-141-5/+50
|
* Exercise the EC parameters code a bit moretb2024-10-121-1/+103
| | | | | | Ensure all builtin curves can be roundtripped through DER as named curves, via explicit parameterization, using uncompressed, compressed and hybrid point formats.
* CRYPTO_mem_leaks* will go away. Remove calls in legacy teststb2024-02-291-2/+1
|
* ec_point_conversion: zap an empty linetb2024-01-181-2/+1
|
* Unifdef OPENSSL_NO_ENGINE in libcrypto regresstb2023-11-191-7/+1
|
* Remove unused prototypetb2023-08-011-3/+1
|
* Remove comment containing an outdated pathtb2023-07-261-2/+1
|
* Fix EC_POINT_is_on_curve() checks.tb2023-07-241-9/+9
| | | | If not even the idiot who invented this API gets this right...