diff options
author | tb <> | 2024-10-26 10:15:19 +0000 |
---|---|---|
committer | tb <> | 2024-10-26 10:15:19 +0000 |
commit | e2a62e818bf165355adbef5a3d01db7e7c51499e (patch) | |
tree | 5d36dfbaefdb2c00198e717b443c590b79828e87 /src/lib/libcrypto/dsa/dsa_pmeth.c | |
parent | c4eb8d5a79a0ea768ecf9ab0dc14b49504631d35 (diff) | |
download | openbsd-e2a62e818bf165355adbef5a3d01db7e7c51499e.tar.gz openbsd-e2a62e818bf165355adbef5a3d01db7e7c51499e.tar.bz2 openbsd-e2a62e818bf165355adbef5a3d01db7e7c51499e.zip |
Add regress coverage for ec_print.c
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.
Diffstat (limited to 'src/lib/libcrypto/dsa/dsa_pmeth.c')
0 files changed, 0 insertions, 0 deletions