Extend docs for EC_POINT conversion functions
authorNicola Tuveri <nic.tuv@gmail.com>
Mon, 11 Nov 2019 22:52:00 +0000 (00:52 +0200)
committerNicola Tuveri <nic.tuv@gmail.com>
Wed, 13 Nov 2019 16:02:51 +0000 (18:02 +0200)
commit3cc26f2eba8a8c16ac559e68c05c094d7ea6bd8b
tree4556378c60968fb26d06a618caea4de11a123977
parent35ed029b5a488924890fda2487c87f664361a33b
Extend docs for EC_POINT conversion functions

Add more explicit documentation about the relation between
EC_POINT_point2oct(), EC_POINT_point2hex(), EC_POINT_point2bn() and
their reverse.

In particular highlight that EC_POINT_point2oct() and
EC_POINT_oct2point() conform to, respectively, Sec. 2.3.3 and Sec. 2.3.4
of the SECG SEC 1 standard (which is the normative reference for the
already mentioned RFC 5480), highlighting with a note how this affect
the encoding/decoding of the point at infinity (which in contrast with
any other valid generic point of a curve is assigned an exceptional
fixed octet string encoding, i.e., 0x00).

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10329)
doc/man3/EC_POINT_new.pod