diff options
| author | tb <> | 2024-11-01 05:20:58 +0000 |
|---|---|---|
| committer | tb <> | 2024-11-01 05:20:58 +0000 |
| commit | 0cb2a2476b758ee5bb2fd68491189400b213a325 (patch) | |
| tree | 4b39e7d5d135d31e112ccfe8357eef5accb5457b /src/lib/libcrypto/cversion.c | |
| parent | 5990e828ab40b8267ccde3e442ba0fba84da9d66 (diff) | |
| download | openbsd-0cb2a2476b758ee5bb2fd68491189400b213a325.tar.gz openbsd-0cb2a2476b758ee5bb2fd68491189400b213a325.tar.bz2 openbsd-0cb2a2476b758ee5bb2fd68491189400b213a325.zip | |
Move point_conversion_t conversion to API boundary
EC_POINT_oct2point() is the only API that needs detailed knowledge about
this incomplete enum. [Arguably, the setters for the EC_KEY and EC_GROUP
member of that type would also need to be able to validate what's being
set, but they can't since they can't fail.] Anyway. Add a helper that lets
EC_POINT_oct2point() translate that enum to its internal representation
at the API boundary and add a check that ensures that we only encode the
point at infinity as the point at infinity.
ok jsing
Diffstat (limited to 'src/lib/libcrypto/cversion.c')
0 files changed, 0 insertions, 0 deletions