Lines Matching refs:parameters
10 For B<DH> FFC key agreement, two classes of domain parameters can be used:
11 "safe" domain parameters that are associated with approved named safe-prime
12 groups, and a class of "FIPS 186-type" domain parameters. FIPS 186-type domain
13 parameters should only be used for backward compatibility with existing
30 =head2 DH and DHX domain parameters
32 In addition to the common FCC parameters that all FFC keytypes should support
33 (see L<EVP_PKEY-FFC(7)/FFC parameters>) the B<DHX> and B<DH> keytype
50 DH/DHX named groups can be easily validated since the parameters are well known.
56 =head2 DH and DHX additional parameters
68 =head2 DH additional domain parameters
85 =head2 DH and DHX domain parameter / key generation parameters
87 In addition to the common FFC key generation parameters that all FFC key types
88 should support (see L<EVP_PKEY-FFC(7)/FFC key generation parameters>) the
105 These are described in L<EVP_PKEY-FFC(7)/FFC key generation parameters>
162 B<DHX> domain parameters can be generated according to B<FIPS 186-4> by calling:
189 A B<DH> key can be generated using domain parameters by calling:
201 To validate B<FIPS 186-4> B<DHX> domain parameters decoded from B<PEM> or
206 to add these parameters to the original key or domain parameters before
209 EVP_PKEY *received_domp = ...; /* parameters received and decoded */
210 unsigned char *seed = ...; /* and additional parameters received */