mirror of
https://github.com/CloverHackyColor/CloverBootloader.git
synced 2024-12-03 13:13:30 +01:00
124 lines
3.8 KiB
Plaintext
124 lines
3.8 KiB
Plaintext
=pod
|
|
|
|
=head1 NAME
|
|
|
|
EVP_PKEY-DSA, EVP_KEYMGMT-DSA - EVP_PKEY DSA keytype and algorithm support
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
For B<DSA> the FIPS186-4 standard specifies that the values used for FFC
|
|
parameter generation are also required for parameter validation.
|
|
This means that optional FFC domain parameter values for I<seed>, I<pcounter>
|
|
and I<gindex> may need to be stored for validation purposes. For B<DSA> these
|
|
fields are not stored in the ASN1 data so they need to be stored externally if
|
|
validation is required.
|
|
|
|
=head2 DSA parameters
|
|
|
|
The B<DSA> key type supports the FFC parameters (see
|
|
L<EVP_PKEY-FFC(7)/FFC parameters>).
|
|
|
|
=head2 DSA key generation parameters
|
|
|
|
The B<DSA> key type supports the FFC key generation parameters (see
|
|
L<EVP_PKEY-FFC(7)/FFC key generation parameters>
|
|
|
|
The following restrictions apply to the "pbits" field:
|
|
|
|
For "fips186_4" this must be either 2048 or 3072.
|
|
For "fips186_2" this must be 1024.
|
|
For "group" this can be any one of 2048, 3072, 4096, 6144 or 8192.
|
|
|
|
=head2 DSA key validation
|
|
|
|
For DSA keys, L<EVP_PKEY_param_check(3)> behaves in the following way:
|
|
The OpenSSL FIPS provider conforms to the rules within the FIPS186-4
|
|
standard for FFC parameter validation. For backwards compatibility the OpenSSL
|
|
default provider uses a much simpler check (see below) for parameter validation,
|
|
unless the seed parameter is set.
|
|
|
|
For DSA keys, L<EVP_PKEY_param_check_quick(3)> behaves in the following way:
|
|
A simple check of L and N and partial g is performed. The default provider
|
|
also supports validation of legacy "fips186_2" keys.
|
|
|
|
For DSA keys, L<EVP_PKEY_public_check(3)>, L<EVP_PKEY_private_check(3)> and
|
|
L<EVP_PKEY_pairwise_check(3)> the OpenSSL default and FIPS providers conform to
|
|
the rules within SP800-56Ar3 for public, private and pairwise tests respectively.
|
|
|
|
=head1 EXAMPLES
|
|
|
|
An B<EVP_PKEY> context can be obtained by calling:
|
|
|
|
EVP_PKEY_CTX *pctx = EVP_PKEY_CTX_new_from_name(NULL, "DSA", NULL);
|
|
|
|
The B<DSA> domain parameters can be generated by calling:
|
|
|
|
unsigned int pbits = 2048;
|
|
unsigned int qbits = 256;
|
|
int gindex = 1;
|
|
OSSL_PARAM params[5];
|
|
EVP_PKEY *param_key = NULL;
|
|
EVP_PKEY_CTX *pctx = NULL;
|
|
|
|
pctx = EVP_PKEY_CTX_new_from_name(NULL, "DSA", NULL);
|
|
EVP_PKEY_paramgen_init(pctx);
|
|
|
|
params[0] = OSSL_PARAM_construct_uint("pbits", &pbits);
|
|
params[1] = OSSL_PARAM_construct_uint("qbits", &qbits);
|
|
params[2] = OSSL_PARAM_construct_int("gindex", &gindex);
|
|
params[3] = OSSL_PARAM_construct_utf8_string("digest", "SHA384", 0);
|
|
params[4] = OSSL_PARAM_construct_end();
|
|
EVP_PKEY_CTX_set_params(pctx, params);
|
|
|
|
EVP_PKEY_generate(pctx, ¶m_key);
|
|
EVP_PKEY_CTX_free(pctx);
|
|
|
|
EVP_PKEY_print_params(bio_out, param_key, 0, NULL);
|
|
|
|
A B<DSA> key can be generated using domain parameters by calling:
|
|
|
|
EVP_PKEY *key = NULL;
|
|
EVP_PKEY_CTX *gctx = NULL;
|
|
|
|
gctx = EVP_PKEY_CTX_new_from_pkey(NULL, param_key, NULL);
|
|
EVP_PKEY_keygen_init(gctx);
|
|
EVP_PKEY_generate(gctx, &key);
|
|
EVP_PKEY_CTX_free(gctx);
|
|
EVP_PKEY_print_private(bio_out, key, 0, NULL);
|
|
|
|
|
|
=head1 CONFORMING TO
|
|
|
|
The following sections of FIPS186-4:
|
|
|
|
=over 4
|
|
|
|
=item A.1.1.2 Generation of Probable Primes p and q Using an Approved Hash Function.
|
|
|
|
=item A.2.3 Generation of canonical generator g.
|
|
|
|
=item A.2.1 Unverifiable Generation of the Generator g.
|
|
|
|
=back
|
|
|
|
=head1 SEE ALSO
|
|
|
|
L<EVP_PKEY-FFC(7)>,
|
|
L<EVP_SIGNATURE-DSA(7)>
|
|
L<EVP_PKEY(3)>,
|
|
L<provider-keymgmt(7)>,
|
|
L<EVP_KEYMGMT(3)>,
|
|
L<OSSL_PROVIDER-default(7)>,
|
|
L<OSSL_PROVIDER-FIPS(7)>
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
Copyright 2020-2022 The OpenSSL Project Authors. All Rights Reserved.
|
|
|
|
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
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
=cut
|