| /src/sys/dev/qat/qat_api/firmware/include/ |
| H A D | icp_qat_fw_mmp_ids.h | 21 * @li 1 input parameters : @link
23 * @li 2 output parameters : @link
29 * @li 3 input parameters : @link
33 * @li 2 output parameters : @link
39 * @li 2 input parameters : @link icp_qat_fw_mmp_ecsm2_point_verify_input_s::x x
41 * @li no output parameters
45 * @li 3 input parameters : @link icp_qat_fw_mmp_ecsm2_sign_rs_input_s::k k
48 * @li 2 output parameters : @link icp_qat_fw_mmp_ecsm2_sign_rs_output_s::r r
53 * @li 5 input parameters : @link icp_qat_fw_mmp_ecsm2_verify_input_s::e e
58 * @li no output parameters
[all …]
|
| /src/crypto/openssl/doc/man3/ |
| H A D | EVP_PKEY_CTX_set_params.pod | 23 transfer of arbitrary key parameters to and from providers.
24 Not all parameters may be supported by all providers.
28 See L<OSSL_PARAM(3)> for information about passing parameters.
36 settable parameters for the current algorithm implementation, i.e. parameters
42 =head2 Parameters section in DESCRIPTION
44 Examples of EVP_PKEY parameters include the following:
46 L<provider-keymgmt(7)/Common parameters>
47 L<provider-keyexch(7)/Key Exchange parameters>
48 L<provider-signature(7)/Signature parameters>
50 L<EVP_PKEY-RSA(7)/Common RSA parameters>
[all …]
|
| H A D | SSL_CTX_set_tmp_dh_callback.pod | 51 (DH parameters) and generate a DH key. The server will always generate
54 As generating DH parameters is extremely time consuming, an application
55 should not generate the parameters on the fly. DH parameters can be reused, as
58 Typically applications should use well known DH parameters that have built-in
60 configure OpenSSL to use the default built-in DH parameters for the B<SSL_CTX>
67 If "auto" DH parameters are switched on then the parameters will be selected to
72 Applications may supply their own DH parameters instead of using the built-in
75 their own DH parameters should call SSL_CTX_set0_tmp_dh_pkey() or
76 SSL_set0_tmp_dh_pkey() to supply the parameters for the B<SSL_CTX> or B<SSL>
77 respectively. The parameters should be supplied in the I<dhpkey> argument as
[all …]
|
| /src/sys/contrib/zstd/lib/dictBuilder/ |
| H A D | fastcover.c | 158 ZDICT_cover_params_t parameters, in FASTCOVER_selectSegment() argument
161 const U32 k = parameters.k; in FASTCOVER_selectSegment()
162 const U32 d = parameters.d; in FASTCOVER_selectSegment()
229 static int FASTCOVER_checkParameters(ZDICT_cover_params_t parameters, in FASTCOVER_checkParameters() argument
232 /* k, d, and f are required parameters */ in FASTCOVER_checkParameters()
233 if (parameters.d == 0 || parameters.k == 0) { in FASTCOVER_checkParameters()
237 if (parameters.d != 6 && parameters.d != 8) { in FASTCOVER_checkParameters()
241 if (parameters.k > maxDictSize) { in FASTCOVER_checkParameters()
245 if (parameters.d > parameters.k) { in FASTCOVER_checkParameters()
253 if (parameters.splitPoint <= 0 || parameters.splitPoint > 1) { in FASTCOVER_checkParameters()
[all …]
|
| H A D | cover.c | 416 ZDICT_cover_params_t parameters) { in COVER_selectSegment() argument
418 const U32 k = parameters.k; in COVER_selectSegment()
419 const U32 d = parameters.d; in COVER_selectSegment()
493 * Check the validity of the parameters.
494 * Returns non-zero if the parameters are valid and 0 otherwise.
496 static int COVER_checkParameters(ZDICT_cover_params_t parameters, in COVER_checkParameters() argument
498 /* k and d are required parameters */ in COVER_checkParameters()
499 if (parameters.d == 0 || parameters.k == 0) { in COVER_checkParameters()
503 if (parameters.k > maxDictSize) { in COVER_checkParameters()
507 if (parameters.d > parameters.k) { in COVER_checkParameters()
[all …]
|
| /src/secure/lib/libcrypto/man/man3/ |
| H A D | EVP_PKEY_CTX_set_params.3 | 85 transfer of arbitrary key parameters to and from providers.
86 Not all parameters may be supported by all providers.
90 See \fBOSSL_PARAM\fR\|(3) for information about passing parameters.
98 settable parameters for the current algorithm implementation, i.e. parameters
103 .SS Parameters
104 .IX Subsection "Parameters"
105 Examples of EVP_PKEY parameters include the following:
107 "Common parameters" in \fBprovider\-keymgmt\fR\|(7)
108 "Key Exchange parameters" in \fBprovider\-keyexch\fR\|(7)
109 "Signature parameters" in \fBprovider\-signature\fR\|(7)
[all …]
|
| H A D | SSL_CTX_set_tmp_dh_callback.3 | 115 (DH parameters) and generate a DH key. The server will always generate
118 As generating DH parameters is extremely time consuming, an application
119 should not generate the parameters on the fly. DH parameters can be reused, as
122 Typically applications should use well known DH parameters that have built\-in
124 configure OpenSSL to use the default built\-in DH parameters for the \fBSSL_CTX\fR
131 If "auto" DH parameters are switched on then the parameters will be selected to
136 Applications may supply their own DH parameters instead of using the built\-in
139 their own DH parameters should call \fBSSL_CTX_set0_tmp_dh_pkey()\fR or
140 \&\fBSSL_set0_tmp_dh_pkey()\fR to supply the parameters for the \fBSSL_CTX\fR or \fBSSL\fR
141 respectively. The parameters should be supplied in the \fIdhpkey\fR argument as
[all …]
|
| /src/crypto/heimdal/doc/doxyout/krb5/man/man3/ |
| H A D | krb5_storage.3 | 178 \fBParameters:\fP
195 \fBParameters:\fP
212 \fBParameters:\fP
229 \fBParameters:\fP
246 \fBParameters:\fP
263 \fBParameters:\fP
280 \fBParameters:\fP
297 \fBParameters:\fP
314 \fBParameters:\fP
331 \fBParameters:\fP
[all …]
|
| H A D | krb5.3 | 183 \fBParameters:\fP
200 \fBParameters:\fP
217 \fBParameters:\fP
255 \fBParameters:\fP
276 \fBParameters:\fP
293 \fBParameters:\fP
312 \fBParameters:\fP
331 \fBParameters:\fP
350 \fBParameters:\fP
369 \fBParameters:\fP
[all …]
|
| H A D | krb5_principal.3 | 91 \fBParameters:\fP
114 \fBParameters:\fP
133 \fBParameters:\fP
150 \fBParameters:\fP
171 \fBParameters:\fP
190 \fBParameters:\fP
214 \fBParameters:\fP
235 \fBParameters:\fP
261 \fBParameters:\fP
278 \fBParameters:\fP
[all …]
|
| H A D | krb5_keytab.3 | 82 \fBParameters:\fP
101 \fBParameters:\fP
118 \fBParameters:\fP
141 \fBParameters:\fP
160 \fBParameters:\fP
177 \fBParameters:\fP
196 \fBParameters:\fP
215 \fBParameters:\fP
232 \fBParameters:\fP
251 \fBParameters:\fP
[all …]
|
| H A D | krb5_crypto.3 | 94 \fBParameters:\fP
111 \fBParameters:\fP
130 \fBParameters:\fP
149 \fBParameters:\fP
168 \fBParameters:\fP
193 \fBParameters:\fP
210 \fBParameters:\fP
237 \fBParameters:\fP
256 \fBParameters:\fP
275 \fBParameters:\fP
[all …]
|
| /src/crypto/openssl/doc/man1/ |
| H A D | openssl-ecparam.pod.in | 34 this command can only create EC parameters from known (named) curves.
46 The EC parameters input format; unspecified by default.
51 The EC parameters output format; the default is B<PEM>.
54 Parameters are encoded as B<EcpkParameters> as specified in IETF RFC 3279.
58 This specifies the input file to read parameters from or standard input if
63 This specifies the output filename parameters to. Standard output is used
71 This option inhibits the output of the encoded version of the parameters.
75 This option prints out the EC parameters in human readable form.
79 Validate the elliptic curve parameters.
83 Validate the elliptic name curve parameters by checking if the curve parameters
[all …]
|
| /src/secure/usr.bin/openssl/man/ |
| H A D | openssl-ecparam.1 | 98 this command can only create EC parameters from known (named) curves.
106 The EC parameters input format; unspecified by default.
110 The EC parameters output format; the default is \fBPEM\fR.
113 Parameters are encoded as \fBEcpkParameters\fR as specified in IETF RFC 3279.
116 This specifies the input file to read parameters from or standard input if
120 This specifies the output filename parameters to. Standard output is used
127 This option inhibits the output of the encoded version of the parameters.
130 This option prints out the EC parameters in human readable form.
133 Validate the elliptic curve parameters.
136 Validate the elliptic name curve parameters by checking if the curve parameters
[all …]
|
| /src/crypto/heimdal/doc/doxyout/hx509/man/man3/ |
| H A D | hx509_cert.3 | 118 \fBParameters:\fP
137 \fBParameters:\fP
158 \fBParameters:\fP
177 \fBParameters:\fP
198 \fBParameters:\fP
208 \fBParameters:\fP
225 \fBParameters:\fP
244 \fBParameters:\fP
259 \fBParameters:\fP
276 \fBParameters:\fP
[all …]
|
| H A D | hx509_ca.3 | 107 \fBParameters:\fP
128 \fBParameters:\fP
149 \fBParameters:\fP
172 \fBParameters:\fP
193 \fBParameters:\fP
212 \fBParameters:\fP
231 \fBParameters:\fP
250 \fBParameters:\fP
271 \fBParameters:\fP
290 \fBParameters:\fP
[all …]
|
| H A D | hx509_verify.3 | 67 \fBParameters:\fP
79 \fBParameters:\fP
98 \fBParameters:\fP
115 \fBParameters:\fP
127 \fBParameters:\fP
146 \fBParameters:\fP
167 \fBParameters:\fP
194 \fBParameters:\fP
206 \fBParameters:\fP
218 \fBParameters:\fP
[all …]
|
| /src/crypto/heimdal/doc/doxyout/hcrypto/man/man3/ |
| H A D | hcrypto_dh.3 | 67 \fBParameters:\fP
69 \fIdh\fP the local peer DH parameters.
71 \fIpub_key\fP the remote peer public key parameters.
100 \fBParameters:\fP
121 \fBParameters:\fP
131 \fBParameters:\fP
144 Generate DH parameters for the DH object give parameters.
146 \fBParameters:\fP
148 \fIdh\fP The DH object to generate parameters for.
154 \fIcb\fP Callback parameters to show progress, can be NULL.
[all …]
|
| H A D | hcrypto_des.3 | 78 \fBParameters:\fP
98 \fBParameters:\fP
120 \fBParameters:\fP
142 \fBParameters:\fP
157 \fBParameters:\fP
177 \fBParameters:\fP
195 \fBParameters:\fP
219 \fBParameters:\fP
233 \fBParameters:\fP
243 \fBParameters:\fP
[all …]
|
| H A D | hcrypto_evp.3 | 325 \fBParameters:\fP
384 \fBParameters:\fP
403 \fBParameters:\fP
418 \fBParameters:\fP
433 \fBParameters:\fP
452 \fBParameters:\fP
467 \fBParameters:\fP
482 \fBParameters:\fP
496 \fBParameters:\fP
511 \fBParameters:\fP
[all …]
|
| /src/secure/lib/libcrypto/man/man7/ |
| H A D | EVP_PKEY-DH.7 | 72 parameters can be used: "safe" domain parameters that are associated with
74 parameters. FIPS186\-type domain parameters should only be used for backward
84 of the nuances associated with FIPS186\-4 style parameters as discussed in
86 .SS "DH and DHX domain parameters"
87 .IX Subsection "DH and DHX domain parameters"
88 In addition to the common FFC parameters that all FFC keytypes should support
89 (see "FFC parameters" in \fBEVP_PKEY\-FFC\fR\|(7)) the \fBDHX\fR and \fBDH\fR keytype
103 DH/DHX named groups can be easily validated since the parameters are well known.
106 .SS "DH and DHX additional parameters"
107 .IX Subsection "DH and DHX additional parameters"
[all …]
|
| H A D | EVP_CIPHER-NULL.7 | 78 .SS Parameters
79 .IX Subsection "Parameters"
80 This implementation supports the following parameters:
82 \fIGettable EVP_CIPHER parameters\fR
83 .IX Subsection "Gettable EVP_CIPHER parameters"
85 See "Gettable EVP_CIPHER parameters" in \fBEVP_EncryptInit\fR\|(3)
87 \fIGettable EVP_CIPHER_CTX parameters\fR
88 .IX Subsection "Gettable EVP_CIPHER_CTX parameters"
98 See "PARAMETERS" in \fBEVP_EncryptInit\fR\|(3) for further information.
100 \fISettable EVP_CIPHER_CTX parameters\fR
[all …]
|
| /src/usr.sbin/jls/ |
| H A D | jls.8 | 47 .Ar parameters ,
48 one jail per line (unless the parameters themselves contain newlines).
51 will show all available jail parameters.
52 A list of available parameters can be retrieved via
56 for a description of some core parameters.
59 .Ar parameters
92 Print a header line containing the parameters listed.
93 If no parameters are given on the command line,
101 Print parameters in
104 If no parameters are given on the command line,
[all …]
|
| /src/crypto/openssl/doc/man7/ |
| H A D | EVP_PKEY-DH.pod | 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
[all …]
|
| /src/crypto/heimdal/doc/doxyout/ntlm/man/man3/ |
| H A D | ntlm_core.3 | 76 \fBParameters:\fP
97 \fBParameters:\fP
120 \fBParameters:\fP
147 \fBParameters:\fP
168 \fBParameters:\fP
197 \fBParameters:\fP
216 \fBParameters:\fP
235 \fBParameters:\fP
252 \fBParameters:\fP
269 \fBParameters:\fP
[all …]
|