summaryrefslogtreecommitdiff
path: root/src/lib/libc
diff options
context:
space:
mode:
authortb <>2025-04-25 19:57:12 +0000
committertb <>2025-04-25 19:57:12 +0000
commitcb56cb39e4330bac5b137be25dddcb89c34eee5e (patch)
tree861ff688d2e1eb96feb6980c81276954e5ebafe4 /src/lib/libc
parent120a986cb6f325a834aa58315f1c744f3d9c8165 (diff)
downloadopenbsd-cb56cb39e4330bac5b137be25dddcb89c34eee5e.tar.gz
openbsd-cb56cb39e4330bac5b137be25dddcb89c34eee5e.tar.bz2
openbsd-cb56cb39e4330bac5b137be25dddcb89c34eee5e.zip
Rework EC documentation
This replaces the giant, poor quality and outdated EC_GROUP_copy.3, EC_GROUP_new.3, and EC_POINT_new.3 manuals with seven new manuals written from scratch. * EC_GROUP_new_by_curve_name() is the entry point for builtin curves, * EC_GROUP_new_curve_GFp() describes lower level API that should not usually be needed apart from a handful of accessors. * EC_GROUP_check() contains two functions that applications should not need because either you know for certain something is an elliptic curve (so these checks are pointless) or you should not use it. * EC_GROUP_get_curve_name() describes some low level ASN.1 footguns and corresponding getters. * EC_POINT_new() contains the simple EC_POINT allocation and freeing API * EC_POINT_get_affine_coordinates() contains the coordinate accessors * EC_POINT_point2oct() is about encoding elliptic curve points While all this is quite far from perfect, the diff is getting too big and it will be easier to improve this in tree. It is definitely more repetitive than I would like it to be. Reviews, tweaks and general feedback are of course welcome. discussed with jsing
Diffstat (limited to 'src/lib/libc')
0 files changed, 0 insertions, 0 deletions