.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "EVP_KDF-X963 7ssl" .TH EVP_KDF-X963 7ssl 2024-10-23 3.4.0 OpenSSL .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME EVP_KDF\-X963 \- The X9.63\-2001 EVP_KDF implementation .SH DESCRIPTION .IX Header "DESCRIPTION" The EVP_KDF\-X963 algorithm implements the key derivation function (X963KDF). X963KDF is used by Cryptographic Message Syntax (CMS) for EC KeyAgreement, to derive a key using input such as a shared secret key and shared info. .PP The output is considered to be keying material. .SS Identity .IX Subsection "Identity" "X963KDF" is the name for this implementation; it can be used with the \fBEVP_KDF_fetch()\fR function. .SS "Supported parameters" .IX Subsection "Supported parameters" The supported parameters are: .IP """properties"" (\fBOSSL_KDF_PARAM_PROPERTIES\fR) " 4 .IX Item """properties"" (OSSL_KDF_PARAM_PROPERTIES) " .PD 0 .IP """digest"" (\fBOSSL_KDF_PARAM_DIGEST\fR) " 4 .IX Item """digest"" (OSSL_KDF_PARAM_DIGEST) " .PD These parameters work as described in "PARAMETERS" in \fBEVP_KDF\fR\|(3). .IP """key"" (\fBOSSL_KDF_PARAM_KEY\fR) " 4 .IX Item """key"" (OSSL_KDF_PARAM_KEY) " The shared secret used for key derivation. This parameter sets the secret. .IP """info"" (\fBOSSL_KDF_PARAM_INFO\fR) " 4 .IX Item """info"" (OSSL_KDF_PARAM_INFO) " This parameter specifies an optional value for shared info. .PP The OpenSSL FIPS provider also supports the following parameters: .IP """fips-indicator"" (\fBOSSL_KDF_PARAM_FIPS_APPROVED_INDICATOR\fR) " 4 .IX Item """fips-indicator"" (OSSL_KDF_PARAM_FIPS_APPROVED_INDICATOR) " A getter that returns 1 if the operation is FIPS approved, or 0 otherwise. This may be used after calling EVP_KDF_derive. It returns 0 if any "***\-check" related parameter is set to 0 and the check fails. .IP """digest-check"" (\fBOSSL_KDF_PARAM_FIPS_DIGEST_CHECK\fR) " 4 .IX Item """digest-check"" (OSSL_KDF_PARAM_FIPS_DIGEST_CHECK) " The default value of 1 causes an error during \fBEVP_KDF_CTX_set_params()\fR if used digest is not approved. Setting this to zero will ignore the error and set the approved "fips-indicator" to 0. This option breaks FIPS compliance if it causes the approved "fips-indicator" to return 0. .Sp According to ANSI X9.63\-2001, the following are approved digest algorithms: SHA2\-224, SHA2\-256, SHA2\-384, SHA2\-512, SHA2\-512/224, SHA2\-512/256, SHA3\-224, SHA3\-256, SHA3\-384, SHA3\-512. .IP """key-check"" (\fBOSSL_KDF_PARAM_FIPS_KEY_CHECK\fR) " 4 .IX Item """key-check"" (OSSL_KDF_PARAM_FIPS_KEY_CHECK) " The default value of 1 causes an error during \fBEVP_KDF_CTX_set_params()\fR if the length of used key-derivation key (\fBOSSL_KDF_PARAM_KEY\fR) is shorter than 112 bits. Setting this to zero will ignore the error and set the approved "fips-indicator" to 0. This option breaks FIPS compliance if it causes the approved "fips-indicator" to return 0. .SH NOTES .IX Header "NOTES" X963KDF is very similar to the SSKDF that uses a digest as the auxiliary function, X963KDF appends the counter to the secret, whereas SSKDF prepends the counter. .PP A context for X963KDF can be obtained by calling: .PP .Vb 2 \& EVP_KDF *kdf = EVP_KDF_fetch(NULL, "X963KDF", NULL); \& EVP_KDF_CTX *kctx = EVP_KDF_CTX_new(kdf); .Ve .PP The output length of an X963KDF is specified via the \fIkeylen\fR parameter to the \fBEVP_KDF_derive\fR\|(3) function. .SH EXAMPLES .IX Header "EXAMPLES" This example derives 10 bytes, with the secret key "secret" and sharedinfo value "label": .PP .Vb 4 \& EVP_KDF *kdf; \& EVP_KDF_CTX *kctx; \& unsigned char out[10]; \& OSSL_PARAM params[4], *p = params; \& \& kdf = EVP_KDF_fetch(NULL, "X963KDF", NULL); \& kctx = EVP_KDF_CTX_new(kdf); \& EVP_KDF_free(kdf); \& \& *p++ = OSSL_PARAM_construct_utf8_string(OSSL_KDF_PARAM_DIGEST, \& SN_sha256, strlen(SN_sha256)); \& *p++ = OSSL_PARAM_construct_octet_string(OSSL_KDF_PARAM_SECRET, \& "secret", (size_t)6); \& *p++ = OSSL_PARAM_construct_octet_string(OSSL_KDF_PARAM_INFO, \& "label", (size_t)5); \& *p = OSSL_PARAM_construct_end(); \& if (EVP_KDF_derive(kctx, out, sizeof(out), params) <= 0) { \& error("EVP_KDF_derive"); \& } \& \& EVP_KDF_CTX_free(kctx); .Ve .SH "CONFORMING TO" .IX Header "CONFORMING TO" "SEC 1: Elliptic Curve Cryptography" .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBEVP_KDF\fR\|(3), \&\fBEVP_KDF_CTX_new\fR\|(3), \&\fBEVP_KDF_CTX_free\fR\|(3), \&\fBEVP_KDF_CTX_set_params\fR\|(3), \&\fBEVP_KDF_CTX_get_kdf_size\fR\|(3), \&\fBEVP_KDF_derive\fR\|(3), "PARAMETERS" in \fBEVP_KDF\fR\|(3) .SH HISTORY .IX Header "HISTORY" This functionality was added in OpenSSL 3.0. .SH COPYRIGHT .IX Header "COPYRIGHT" Copyright 2019\-2024 The OpenSSL Project Authors. All Rights Reserved. .PP Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at .