summaryrefslogtreecommitdiff
path: root/src/lib
diff options
context:
space:
mode:
authorschwarze <>2021-09-14 13:47:59 +0000
committerschwarze <>2021-09-14 13:47:59 +0000
commitac4b6f6c2f01c17b974a21746ca2b53a599223d2 (patch)
treef8ec0f96f2541bb24731b5bea647354efd0aeb22 /src/lib
parentb5ef4f1de7fa055f50f8a5e1d408a91616fad899 (diff)
downloadopenbsd-ac4b6f6c2f01c17b974a21746ca2b53a599223d2.tar.gz
openbsd-ac4b6f6c2f01c17b974a21746ca2b53a599223d2.tar.bz2
openbsd-ac4b6f6c2f01c17b974a21746ca2b53a599223d2.zip
As suggested by tb@, merge the description of OPENSSL_EC_NAMED_CURVE
and OPENSSL_EC_EXPLICIT_CURVE from OpenSSL commit 146ca72c Feb 19 14:35:43 2015 +0000 after tb@ changed the default from 0 to OPENSSL_EC_NAMED_CURVE in ec/ec_lib.c rev. 1.41, which is the same default that OpenSSL uses since 1.1.0. While merging, drop the description of the pre-1.1.0 behaviour. It seems irrelevant to me because tb@ found no application in Debian codesearch using OPENSSL_EC_EXPLICIT_CURVE. A former devious default that was probably never relied upon by anyone does not need to be documented.
Diffstat (limited to 'src/lib')
-rw-r--r--src/lib/libcrypto/man/EC_GROUP_copy.324
1 files changed, 15 insertions, 9 deletions
diff --git a/src/lib/libcrypto/man/EC_GROUP_copy.3 b/src/lib/libcrypto/man/EC_GROUP_copy.3
index a69017fa3e..671544853a 100644
--- a/src/lib/libcrypto/man/EC_GROUP_copy.3
+++ b/src/lib/libcrypto/man/EC_GROUP_copy.3
@@ -1,8 +1,9 @@
1.\" $OpenBSD: EC_GROUP_copy.3,v 1.11 2021/09/11 17:59:04 schwarze Exp $ 1.\" $OpenBSD: EC_GROUP_copy.3,v 1.12 2021/09/14 13:47:59 schwarze Exp $
2.\" full merge up to: OpenSSL aafbe1cc Jun 12 23:42:08 2013 +0100 2.\" full merge up to: OpenSSL d900a015 Oct 8 14:40:42 2015 +0200
3.\" selective merge up to: OpenSSL 24c23e1f Aug 22 10:51:25 2019 +0530 3.\" selective merge up to: OpenSSL 24c23e1f Aug 22 10:51:25 2019 +0530
4.\" 4.\"
5.\" This file was written by Matt Caswell <matt@openssl.org> 5.\" This file was written by Matt Caswell <matt@openssl.org>,
6.\" Dr. Stephen Henson <steve@openssl.org>,
6.\" and Jayaram X Matta <jayaramx.matta@intel.com>. 7.\" and Jayaram X Matta <jayaramx.matta@intel.com>.
7.\" Copyright (c) 2013, 2015, 2019 The OpenSSL Project. All rights reserved. 8.\" Copyright (c) 2013, 2015, 2019 The OpenSSL Project. All rights reserved.
8.\" 9.\"
@@ -50,7 +51,7 @@
50.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 51.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
51.\" OF THE POSSIBILITY OF SUCH DAMAGE. 52.\" OF THE POSSIBILITY OF SUCH DAMAGE.
52.\" 53.\"
53.Dd $Mdocdate: September 11 2021 $ 54.Dd $Mdocdate: September 14 2021 $
54.Dt EC_GROUP_COPY 3 55.Dt EC_GROUP_COPY 3
55.Os 56.Os
56.Sh NAME 57.Sh NAME
@@ -286,16 +287,21 @@ If a curve does not have a NID associated with it, then
286will return 287will return
287.Dv NID_undef . 288.Dv NID_undef .
288.Pp 289.Pp
289The asn1_flag value on a curve is used to determine whether there is a 290The asn1_flag value is used to determine whether the curve encoding
290specific ASN.1 OID to describe the curve or not. 291uses explicit parameters or a named curve using an ASN.1 OID:
291If the asn1_flag is 1 then this is a named curve with an associated ASN.1 OID. 292many applications only support the latter form.
292If not then asn1_flag is 0. 293If asn1_flag is the default value
294.Dv OPENSSL_EC_NAMED_CURVE ,
295then the named curve form is used and the parameters must have a
296corresponding named curve NID set.
297If asn1_flags is
298.Dv OPENSSL_EC_EXPLICIT_CURVE ,
299the parameters are explicitly encoded.
293The functions 300The functions
294.Fn EC_GROUP_get_asn1_flag 301.Fn EC_GROUP_get_asn1_flag
295and 302and
296.Fn EC_GROUP_set_asn1_flag 303.Fn EC_GROUP_set_asn1_flag
297get and set the status of the asn1_flag for the curve. 304get and set the status of the asn1_flag for the curve.
298If set, then the curve_name must also be set.
299.Pp 305.Pp
300The point_conversion_form for a curve controls how 306The point_conversion_form for a curve controls how
301.Vt EC_POINT 307.Vt EC_POINT