Home
last modified time | relevance | path

Searched full:parameters (Results 1 – 25 of 3541) sorted by relevance

12345678910>>...142

/freebsd/sys/dev/qat/qat_api/firmware/include/
H A Dicp_qat_fw_mmp_ids.h22 * @li 1 input parameters : @link
24 * @li 2 output parameters : @link
30 * @li 3 input parameters : @link
34 * @li 2 output parameters : @link
40 * @li 2 input parameters : @link icp_qat_fw_mmp_ecsm2_point_verify_input_s::x x
42 * @li no output parameters
46 * @li 3 input parameters : @link icp_qat_fw_mmp_ecsm2_sign_rs_input_s::k k
49 * @li 2 output parameters : @link icp_qat_fw_mmp_ecsm2_sign_rs_output_s::r r
54 * @li 5 input parameters : @link icp_qat_fw_mmp_ecsm2_verify_input_s::e e
59 * @li no output parameters
[all …]
/freebsd/sys/contrib/zstd/lib/dictBuilder/
H A Dfastcover.c158 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 Dcover.c416 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 …]
/freebsd/crypto/openssl/doc/man3/
H A DEVP_PKEY_CTX_set_params.pod23 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
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>
40 =head2 Parameters global() section in DESCRIPTION
[all...]
H A DSSL_CTX_set_tmp_dh_callback.pod51 (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>
65 If "auto" DH parameters are switched on then the parameters will be selected to
70 Applications may supply their own DH parameters instead of using the built-in
73 their own DH parameters should call SSL_CTX_set0_tmp_dh_pkey() or
74 SSL_set0_tmp_dh_pkey() to supply the parameters for the B<SSL_CTX> or B<SSL>
75 respectively. The parameters should be supplied in the I<dhpkey> argument as
[all …]
/freebsd/crypto/heimdal/doc/doxyout/krb5/man/man3/
H A Dkrb5_storage.3178 \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 Dkrb5.3183 \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 Dkrb5_keytab.382 \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 Dkrb5_principal.391 \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 Dkrb5_crypto.394 \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 …]
H A Dkrb5_support.397 \fBParameters:\fP
134 \fBParameters:\fP
178 \fBParameters:\fP
195 \fBParameters:\fP
207 \fBParameters:\fP
226 \fBParameters:\fP
247 \fBParameters:\fP
266 \fBParameters:\fP
285 \fBParameters:\fP
306 \fBParameters:\fP
[all …]
/freebsd/crypto/openssl/doc/man1/
H A Dopenssl-ecparam.pod.in34 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 filename to read parameters from or standard input if
63 This specifies the output filename parameters to. Standard output is used
69 This option inhibits the output of the encoded version of the parameters.
73 This option prints out the EC parameters in human readable form.
77 Validate the elliptic curve parameters.
81 Validate the elliptic name curve parameters by checking if the curve parameters
[all …]
/freebsd/crypto/heimdal/doc/doxyout/hx509/man/man3/
H A Dhx509_cert.3118 \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 Dhx509_ca.3107 \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 Dhx509_verify.367 \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 …]
/freebsd/crypto/heimdal/doc/doxyout/hcrypto/man/man3/
H A Dhcrypto_dh.367 \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 Dhcrypto_des.378 \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 Dhcrypto_evp.3325 \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 …]
/freebsd/secure/lib/libcrypto/man/man3/
H A DEVP_PKEY_CTX_set_params.3158 transfer of arbitrary key parameters to and from providers.
159 Not all parameters may be supported by all providers.
161 See \s-1\fBOSSL_PARAM\s0\fR\|(3) for more information on parameters.
169 settable parameters for the current algorithm implementation, i.e. parameters
174 .SS "Parameters"
175 .IX Subsection "Parameters"
176 Examples of \s-1EVP_PKEY\s0 parameters include the following:
178 \&\*(L"Common parameters\*(R" in \fBprovider\-keymgmt\fR\|(7)
179 \&\*(L"Key Exchange parameters\*(R" in \fBprovider\-keyexch\fR\|(7)
180 \&\*(L"Signature parameters\*(R" in \fBprovider\-signature\fR\|(7)
[all …]
/freebsd/secure/usr.bin/openssl/man/
H A Dopenssl-ecparam.1170 this command can only create \s-1EC\s0 parameters from known (named) curves.
178 The \s-1EC\s0 parameters input format; unspecified by default.
182 The \s-1EC\s0 parameters output format; the default is \fB\s-1PEM\s0\fR.
185 Parameters are encoded as \fBEcpkParameters\fR as specified in \s-1IETF RFC 3279.\s0
188 This specifies the input filename to read parameters from or standard input if
192 This specifies the output filename parameters to. Standard output is used
197 This option inhibits the output of the encoded version of the parameters.
200 This option prints out the \s-1EC\s0 parameters in human readable form.
203 Validate the elliptic curve parameters.
206 Validate the elliptic name curve parameters by checking if the curve parameters
[all …]
/freebsd/usr.sbin/jls/
H A Djls.844 .Ar parameters ,
47 which will show all available jail parameters.
48 A list of available parameters can be retrieved via
52 for a description of some core parameters.
55 .Ar parameters
76 Print a header line containing the parameters listed.
77 If no parameters are given on the command line,
85 Print parameters in
88 If no parameters are given on the command line,
92 Put quotes around parameters if they contain spaces or quotes, or are
[all …]
/freebsd/crypto/openssl/doc/man7/
H A DEVP_PKEY-DH.pod11 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 …]
/freebsd/crypto/heimdal/doc/doxyout/ntlm/man/man3/
H A Dntlm_core.376 \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 …]
/freebsd/secure/lib/libcrypto/man/man7/
H A DEVP_PKEY-DH.7144 For \fB\s-1DH\s0\fR \s-1FFC\s0 key agreement, two classes of domain parameters can be used:
145 \&\*(L"safe\*(R" domain parameters that are associated with approved named safe-prime
146 groups, and a class of \*(L"FIPS186\-type\*(R" domain parameters. FIPS186\-type domain
147 parameters should only be used for backward compatibility with existing
156 of the nuances associated with \s-1FIPS186\-4\s0 style parameters as discussed in
158 .SS "\s-1DH\s0 and \s-1DHX\s0 domain parameters"
159 .IX Subsection "DH and DHX domain parameters"
160 In addition to the common \s-1FCC\s0 parameters that all \s-1FFC\s0 keytypes should support
161 (see \*(L"\s-1FFC\s0 parameters\*(R" in \s-1\fBEVP_PKEY\-FFC\s0\fR\|(7)) the \fB\s-1DHX\s0\fR and \…
176 \&\s-1DH/DHX\s0 named groups can be easily validated since the parameters are well known.
[all …]
/freebsd/usr.sbin/wpa/hostapd/
H A Dhostapd.conf.544 The configuration file consists of global parameters and domain
61 .Sh GLOBAL PARAMETERS
62 The following parameters are recognized:
94 .Sh IEEE 802.1X-2004 PARAMETERS
95 The following parameters are recognized:
118 .\" .Sh IEEE 802.11f - IAPP PARAMETERS
119 .\" The following parameters are recognized:
124 .Sh RADIUS CLIENT PARAMETERS
125 The following parameters are recognized:
132 RADIUS authentication server parameters.
[all …]

12345678910>>...142