Lines Matching refs:I
19 The B<DH> key type uses PKCS#3 format which saves I<p> and I<g>, but not the
20 I<q> value.
21 The B<DHX> key type uses X9.42 format which saves the value of I<q> and this
37 with known values for I<p>, I<q> and I<g>.
47 For protocols that only transfer I<p> and I<g> the value of I<q> can also be
77 based on the size of I<p>.
127 BN_num_bits(I<q>)). The minimum value that this can be set to is 2 * s.
138 I<seed>, I<pcounter> and I<gindex> or I<hindex> may need to be stored for
140 For B<DHX> the I<seed> and I<pcounter> can be stored in ASN1 data
141 (but the I<gindex> or I<hindex> cannot be stored). It is recommended to use a
147 parameters conform to FIPS186-4 as defined in SP800-56Ar3 I<Assurances of
150 The OpenSSL default provider uses simpler checks that allows there to be no I<q>
152 test the I<p> value for being a prime (and a safe prime if I<q> is missing)
157 I<FFC Full Public-Key Validation>.
160 I<FFC Partial Public-Key Validation> when the key is an approved named safe
164 according to SP800-56Ar3. The OpenSSL FIPS provider requires the value of I<q>
166 For backwards compatibility the OpenSSL default provider only requires I<p> to
170 I<Owner Assurance of Pair-wise Consistency>.