| /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
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()
403 ZDICT_cover_params_t parameters, in FASTCOVER_buildDictionary() argument
[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()
496 static int COVER_checkParameters(ZDICT_cover_params_t parameters, in COVER_checkParameters() argument
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()
511 if (parameters.splitPoint <= 0 || parameters.splitPoint > 1){ in COVER_checkParameters()
686 ZDICT_cover_params_t parameters) { in COVER_buildDictionary() argument
691 (U32)dictBufferCapacity, (U32)ctx->suffixSize, parameters.k, 4); in COVER_buildDictionary()
[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
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>
51 L<EVP_PKEY-RSA(7)/RSA key generation 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 …]
|
| H A D | EVP_PKEY_fromdata.pod | 6 - functions to create keys and key parameters from user data
31 for creating a key or key parameters from user data.
33 EVP_PKEY_fromdata() creates the structure to store a key or key parameters,
37 The parameters that can be used for various types of key are as described by
38 the various "Common parameters" sections of the
39 L<B<EVP_PKEY-RSA>(7)|EVP_PKEY-RSA(7)/Common RSA parameters>,
40 L<B<EVP_PKEY-DSA>(7)|EVP_PKEY-DSA(7)/Common DSA & DH parameters>,
41 L<B<EVP_PKEY-DH>(7)|EVP_PKEY-DH(7)/Common DH parameters>,
42 L<B<EVP_PKEY-EC>(7)|EVP_PKEY-EC(7)/Common EC parameters>,
43 L<B<EVP_PKEY-ED448>(7)|EVP_PKEY-ED448(7)/Common X25519, X448, ED25519 and ED448 parameters>,
[all …]
|
| H A D | EVP_PKEY_copy_parameters.pod | 29 parameters of B<pkey> are missing and 0 if they are present or the algorithm
30 doesn't use parameters.
32 The function EVP_PKEY_copy_parameters() copies the parameters from key
33 B<from> to key B<to>. An error is returned if the parameters are missing in
34 B<from> or present in both B<from> and B<to> and mismatch. If the parameters
37 The function EVP_PKEY_parameters_eq() checks the parameters of keys
41 including their parameters if they are available.
47 parameters are sometimes omitted from a public key if they are inherited from
54 The function EVP_PKEY_cmp() previously only checked the key parameters
67 the key parameters (if there are any)
[all …]
|
| H A D | EVP_PKEY_keygen.pod | 41 key parameters, often called domain parameters but not necessarily limited
43 may want to set user provided generation parameters that further affect key
48 functions to set user provided parameters, and finally the key parameter or
58 parameters are generated.
60 After initialization, generation parameters may be provided with
65 parameters or key are written to I<*ppkey>. If I<*ppkey> is NULL when this
79 The function EVP_PKEY_CTX_get_keygen_info() returns parameters associated
81 parameters available is returned. Any non negative value returns the value of
117 no further parameters are needed. Other key types may be possible if they are
119 key types as long as they do not require further parameters.
[all …]
|
| H A D | DH_new_by_nid.pod | 5 DH_new_by_nid, DH_get_nid - create or get DH named parameters
21 DH_new_by_nid() creates and returns a DH structure containing named parameters
27 DH_get_nid() determines if the parameters contained in B<dh> match
29 parameters or B<NID_undef> if there is no match.
34 DH_new_by_nid() returns a set of DH parameters or B<NULL> if an error occurred.
36 DH_get_nid() returns the NID of the matching set of parameters for p and g
|
| H A D | EVP_PKEY_CTX_get_algor.pod | 46 B<EVP_I<TYPE>_CTX_get_algor_params>() attempts to retrieve the I<parameters>
48 populates I<alg->parameters> with it.
51 If I<< alg->parameters >> is NULL, space will be allocated automatically, and
52 assigned to I<< alg->parameters >>.
53 If I<< alg->parameters >> is not NULL, its previous contents will be overwritten
54 with the retrieved AlgorithmIdentifier parameters. Beware!
56 B<EVP_I<TYPE>_CTX_set_algor_params>() attempts to pass I<< alg->parameters >>
|
| H A D | SSL_CTX_set_srp_password.pod | 55 These functions provide access to SRP (Secure Remote Password) parameters,
81 The callback parameters are the SSL connection B<s>, a writable error flag B<ad>
84 SSL_set_srp_server_param() with the appropriate parameters for the received
95 The callback parameters are the SSL connection B<s> and the extra argument B<arg>
104 receiving the server SRP proposed parameters.
105 The callback parameters are the SSL connection B<s> and the extra argument B<arg>
107 The callback should return a positive value to accept the server parameters.
108 Returning 0 or a negative value will abort the connection. The server parameters
112 If no callback is set the g and N parameters will be checked against
115 The SSL_set_srp_server_param() function sets all SRP parameters for
[all …]
|
| H A D | SSL_CTX_get0_param.pod | 7 get and set verification parameters
27 the verification parameters for B<ctx> or B<ssl> respectively. The returned
30 SSL_CTX_set1_param() and SSL_set1_param() set the verification parameters
34 set the purpose parameter on the verification parameters object. These functions
38 which set the trust parameter on the verification parameters object. These
43 Typically parameters are retrieved from an B<SSL_CTX> or B<SSL> structure
|
| H A D | EVP_KDF.pod | 105 EVP_KDF_derive() processes any parameters in I<Params> and then derives
113 The set of parameters given with I<params> determine exactly what
114 parameters should be retrieved.
118 EVP_KDF_CTX_get_params() retrieves chosen parameters, given the
120 The set of parameters given with I<params> determine exactly what
121 parameters should be retrieved.
125 EVP_KDF_CTX_set_params() passes chosen parameters to the underlying
127 The set of parameters given with I<params> determine exactly what
128 parameters are passed down.
135 the retrievable and settable parameters. EVP_KDF_gettable_params()
[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>.
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
88 Use the EC parameters with the specified 'short' name. Use B<-list_curves>
[all …]
|
| H A D | openssl-dhparam.pod.in | 35 parameters.
53 This specifies the input file to read parameters from or standard input if
58 This specifies the output file to write parameters to.
66 If this option is used, DSA rather than DH parameters are read or created;
71 Beware that with such DSA-style DH parameters, a fresh DH key should be
77 Performs numerous checks to see if the supplied parameters are valid and
83 input file is ignored and parameters are generated instead. If not
84 present but I<numbits> is present, parameters are generated with the
91 the input file is ignored and parameters are generated instead. If
93 present, parameters are generated with a default length of 2048 bits.
[all …]
|
| H A D | openssl-pkeyparam.pod.in | 25 This command processes public key algorithm parameters.
38 This specifies the input file to read parameters from or standard input if
43 This specifies the output filename to write parameters to or standard output if
51 Prints out the parameters in plain text in addition to the encoded version.
55 Do not output the encoded version of the parameters.
59 This option checks the correctness of parameters.
69 Print out text version of parameters:
|
| H A D | openssl-dsaparam.pod.in | 31 DSA parameters is often used to generate several distinct keys.
43 The DSA parameters input format; unspecified by default.
48 The DSA parameters output format; the default is B<PEM>.
56 This specifies the input file to read parameters from or standard input if
62 This specifies the output file to write parameters to. Standard output is used
70 This option inhibits the output of the encoded version of the parameters.
74 This option prints out the DSA parameters in human readable form.
79 parameters.
|
| /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 …]
|
| H A D | EVP_PKEY-HMAC.pod | 22 =head2 Common MAC parameters
24 All the B<MAC> keytypes support the following parameters.
38 =head2 CMAC parameters
40 As well as the parameters described above, the B<CMAC> keytype additionally
41 supports the following parameters.
55 =head2 Common MAC key generation parameters
69 =head2 CMAC key generation parameters
71 In addition to the common MAC key generation parameters, the CMAC key generation
|
| H A D | EVP_PKEY-DSA.pod | 19 =head2 DSA parameters
21 The B<DSA> key type supports the FFC parameters (see
22 L<EVP_PKEY-FFC(7)/FFC parameters>).
24 It also supports the following parameters:
36 =head2 DSA key generation parameters
38 The B<DSA> key type supports the FFC key generation parameters (see
39 L<EVP_PKEY-FFC(7)/FFC key generation parameters>
69 The B<DSA> domain parameters can be generated by calling:
93 A B<DSA> key can be generated using domain parameters by calling:
|
| H A D | EVP_CIPHER-NULL.pod | 25 This implementation supports the following parameters:
27 =head3 Gettable EVP_CIPHER parameters
29 See L<EVP_EncryptInit(3)/Gettable EVP_CIPHER parameters>
31 =head3 Gettable EVP_CIPHER_CTX parameters
45 =head3 Settable EVP_CIPHER_CTX parameters
|
| /src/contrib/llvm-project/clang/include/clang/Analysis/ |
| H A D | AnyCall.h | 144 ArrayRef<ParmVarDecl *> parameters() const { in parameters() function
149 return FD->parameters(); in parameters()
151 return MD->parameters(); in parameters()
153 return BD->parameters(); in parameters()
160 param_const_iterator param_begin() const { return parameters().begin(); } in param_begin()
161 param_const_iterator param_end() const { return parameters().end(); } in param_end()
162 size_t param_size() const { return parameters().size(); } in param_size()
163 bool param_empty() const { return parameters().empty(); } in param_empty()
|
| /src/sys/contrib/zstd/lib/ |
| H A D | zdict.h | 254 ZDICT_params_t parameters);
324 ZDICT_cover_params_t parameters);
346 ZDICT_cover_params_t* parameters);
367 ZDICT_fastCover_params_t parameters);
390 ZDICT_fastCover_params_t* parameters);
415 ZDICT_legacy_params_t parameters);
|
| /src/crypto/openssl/doc/designs/ |
| H A D | ossl-provider-load-ex.md | 5 initialization parameters in the OpenSSL configuration file. Otherwise the
12 according to per-application parameters. It's necessary for example for PKCS#11
26 It accepts only parameters of type `OSSL_PARAM_UTF8_STRING` because any
30 Explicitly configured parameters can differ from the parameters named in the
43 2. Load/activate a provider run-time with parameters
50 extra parameters are ignored.
52 In all other cases, the extra parameters provided by the `OSSL_PROVIDER_load_ex`
71 1. We should provide some API function accessing the configuration parameters
|
| /src/contrib/llvm-project/compiler-rt/lib/xray/ |
| H A D | xray_trampoline_arm.S | 16 @ for passing parameters to C/C++ functions.
22 @ Save floating-point parameters of the instrumented function
33 @ Call the handler with 2 parameters in r0 and r1
36 @ Restore floating-point parameters of the instrumented function
65 @ Call the handler with 2 parameters in r0 and r1
79 @ for passing parameters to C/C++ functions.
85 @ Save floating-point parameters of the instrumented function
98 @ Call the handler with 2 parameters in r0 and r1
101 @ Restore floating-point parameters of the instrumented function
|
| /src/crypto/openssl/providers/common/der/ |
| H A D | RSA.asn1 | 26 -- the parameters MUST be present and MUST be NULL.
32 -- parameters MUST be present and MUST be RSAES-OAEP-params.
38 -- parameters MUST be an OCTET STRING.
44 -- parameters MUST be present and MUST be RSASSA-PSS-params.
50 -- the parameters MUST be present and MUST be NULL.
63 -- When id-mgf1 is used in an AlgorithmIdentifier, the parameters
|