Lines Matching full:parameters

11 parameters can be used: "safe" domain parameters that are associated with
13 parameters. FIPS186-type domain parameters should only be used for backward
23 of the nuances associated with FIPS186-4 style parameters as discussed in
26 =head2 DH and DHX domain parameters
28 In addition to the common FFC parameters that all FFC keytypes should support
29 (see L<EVP_PKEY-FFC(7)/FFC parameters>) the B<DHX> and B<DH> keytype
46 DH/DHX named groups can be easily validated since the parameters are well known.
52 =head2 DH and DHX additional parameters
64 =head2 DH additional domain parameters
81 =head2 DH and DHX domain parameter / key generation parameters
83 In addition to the common FFC key generation parameters that all FFC key types
84 should support (see L<EVP_PKEY-FFC(7)/FFC key generation parameters>) the
101 These are described in L<EVP_PKEY-FFC(7)/FFC key generation parameters>
142 B<DH> parameters with named safe prime group instead.
145 L<EVP_PKEY_param_check_quick(3)> behave in the following way: the parameters
147 parameters conform to FIPS186-4 as defined in SP800-56Ar3 I<Assurances of
197 B<DHX> domain parameters can be generated according to B<FIPS186-4> by calling:
224 A B<DH> key can be generated using domain parameters by calling:
236 To validate B<FIPS186-4> B<DHX> domain parameters decoded from B<PEM> or
241 to add these parameters to the original key or domain parameters before
244 EVP_PKEY *received_domp = ...; /* parameters received and decoded */
245 unsigned char *seed = ...; /* and additional parameters received */