Home
last modified time | relevance | path

Searched refs:parameters (Results 1 – 25 of 335) sorted by relevance

12345678910>>...14

/openssl-master/doc/man3/
A DEVP_PKEY_CTX_set_params.pod34 settable parameters for the current algorithm implementation, i.e. parameters
45 L<provider-keymgmt(7)/Common parameters>
46 L<provider-keyexch(7)/Key Exchange parameters>
47 L<provider-signature(7)/Signature parameters>
49 L<EVP_PKEY-RSA(7)/Common RSA parameters>
50 L<EVP_PKEY-RSA(7)/RSA key generation parameters>
51 L<EVP_PKEY-FFC(7)/FFC parameters>
53 L<EVP_PKEY-DSA(7)/DSA parameters>
55 L<EVP_PKEY-DH(7)/DH parameters>
56 L<EVP_PKEY-DH(7)/DH key generation parameters>
[all …]
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 know DH parameters that have built-in
65 If "auto" DH parameters are switched on then the parameters will be selected to
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
76 an B<EVP_PKEY> containg DH parameters. Ownership of the I<dhpkey> value is
84 should use "auto" parameters instead, or call SSL_CTX_set0_tmp_dh_pkey() or
[all …]
A DEVP_PKEY_copy_parameters.pod29 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
40 The function EVP_PKEY_eq() checks the public key components and parameters
47 parameters are sometimes omitted from a public key if they are inherited from
61 parameters of B<pkey> are missing and 0 if they are present or the algorithm
62 doesn't use parameters.
A DDH_new_by_nid.pod5 DH_new_by_nid, DH_get_nid - create or get DH named parameters
20 DH_new_by_nid() creates and returns a DH structure containing named parameters
26 DH_get_nid() determines if the parameters contained in B<dh> match
28 parameters or B<NID_undef> if there is no match.
33 DH_new_by_nid() returns a set of DH parameters or B<NULL> if an error occurred.
35 DH_get_nid() returns the NID of the matching set of parameters for p and g
A DEVP_PKEY_fromdata.pod6 - functions to create keys and key parameters from user data
31 for creating a key or key parameters from user data.
38 diverse "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>,
52 the settable parameters that can be used with EVP_PKEY_fromdata().
64 Only key parameters will be selected.
69 parameters.
[all …]
A DEVP_PKEY_keygen.pod41 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
79 The function EVP_PKEY_CTX_get_keygen_info() returns parameters associated
123 parameters.
125 The meaning of the parameters passed to the callback will depend on the
135 public key components and parameters (if any). An OpenSSL private key is
137 in functions which require the use of a public key or parameters.
[all …]
A DSSL_CTX_set_srp_password.pod55 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
104 receiving the server SRP proposed parameters.
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
116 the connection B<s>. B<N> and B<g> are the SRP group parameters, B<sa> is the
119 The SSL_set_srp_server_param_pw() function sets all SRP parameters for the
[all …]
A DOSSL_PARAM.pod5 OSSL_PARAM - a structure to pass or request object parameters
27 parameters for an object, or wants to find out some parameters of an
34 =item * Setting parameters for some object
41 =item * Request parameters of some object
102 setting parameters) or shall (when requesting parameters) be stored,
141 offers these parameters, i.e. names for parameters provided by the
201 offers these parameters).
227 offers these parameters).
304 This example is for setting parameters on some object:
319 This example is for requesting parameters on some object:
[all …]
A DEVP_KDF.pod113 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.
127 The set of parameters given with I<params> determine exactly what
128 parameters are passed down.
136 returns parameters that can be used with EVP_KDF_get_params().
141 parameters that can be used with EVP_KDF_CTX_get_params().
150 returns the parameters that can be retrieved from the algorithm,
[all …]
A DBN_BLINDING_new.pod49 BN_BLINDING_update() updates the B<BN_BLINDING> parameters by squaring
51 necessary parameters are set, by re-creating the blinding parameters.
78 automatic update of the B<BN_BLINDING> parameters after each use
80 of the B<BN_BLINDING> parameters after a fixed number of uses (currently
82 BN_BLINDING_set_flags() sets the B<BN_BLINDING> parameters flags.
84 BN_BLINDING_create_param() creates new B<BN_BLINDING> parameters
110 parameters or NULL on error.
A DSSL_CTX_get0_param.pod6 get and set verification parameters
20 the verification parameters for B<ctx> or B<ssl> respectively. The returned
23 SSL_CTX_set1_param() and SSL_set1_param() set the verification parameters
28 Typically parameters are retrieved from an B<SSL_CTX> or B<SSL> structure
A DEVP_RAND.pod129 EVP_RAND_instantiate() processes any parameters in I<params> and
168 The set of parameters given with I<params> determine exactly what
169 parameters should be retrieved.
173 EVP_RAND_CTX_get_params() retrieves chosen parameters, given the
175 The set of parameters given with I<params> determine exactly what
176 parameters should be retrieved.
182 The set of parameters given with I<params> determine exactly what
183 parameters are passed down.
275 additional parameters are recognised. Not all
276 parameters are relevant to, or are understood by all DRBG rands:
[all …]
/openssl-master/doc/man1/
A Dopenssl-ecparam.pod.in46 The EC parameters input format; unspecified by default.
51 The EC parameters output format; the default is B<PEM>.
77 Validate the elliptic curve parameters.
81 Validate the elliptic name curve parameters by checking if the curve parameters
87 to get a list of all currently implemented EC parameters.
105 This specifies how the elliptic curve parameters are encoded.
139 To create EC parameters with the group 'prime192v1':
143 To create EC parameters with explicit parameters:
147 To validate given EC parameters:
151 To create EC parameters and a private key:
[all …]
A Dopenssl-dhparam.pod.in33 parameters.
56 This specifies the output filename parameters to. Standard output is used
62 If this option is used, DSA rather than DH parameters are read or created;
69 parameters, a fresh DH key should be created for each use to
74 Performs numerous checks to see if the supplied parameters are valid and
80 input file is ignored and parameters are generated instead. If not
81 present but I<numbits> is present, parameters are generated with the
88 the input file is ignored and parameters are generated instead. If
90 present, parameters are generated with a default length of 2048 bits.
95 This option inhibits the output of the encoded version of the parameters.
[all …]
A Dopenssl-pkeyparam.pod.in25 This command processes public key algorithm parameters.
38 This specifies the input filename to read parameters from or standard input if
43 This specifies the output filename to write parameters to or standard output if
48 Prints out the parameters in plain text in addition to the encoded version.
52 Do not output the encoded version of the parameters.
56 This option checks the correctness of parameters.
66 Print out text version of parameters:
A Dopenssl-dsaparam.pod.in29 DSA parameters is often used to generate several distinct keys.
41 The DSA parameters input format; unspecified by default.
46 The DSA parameters output format; the default is B<PEM>.
54 This specifies the input filename to read parameters from or standard input if
60 This specifies the output filename parameters to. Standard output is used
66 This option inhibits the output of the encoded version of the parameters.
70 This option prints out the DSA parameters in human readable form.
75 parameters.
A Dopenssl-genpkey.pod.in106 parameters along with the PEM or DER structure.
297 generate DHX parameters.
308 The type name of DH parameters to generate. Valid values are:
395 Generate an RSA private key using default parameters:
415 Generate DSA key from parameters:
427 Generate a DH key using a DH parameters file:
431 Output DH parameters for safe prime group ffdhe2048:
451 Output 2048 bit DH parameters:
456 Output 2048 bit DH parameters using a generator:
462 Generate EC parameters:
[all …]
/openssl-master/doc/man7/
A DEVP_PKEY-DH.pod10 For B<DH> FFC key agreement, two classes of domain parameters can be used:
11 "safe" domain parameters that are associated with approved named safe-prime
12 groups, and a class of "FIPS 186-type" domain parameters. FIPS 186-type domain
13 parameters should only be used for backward compatibility with existing
30 =head2 DH and DHX domain parameters
33 (see L<EVP_PKEY-FFC(7)/FFC parameters>) the B<DHX> and B<DH> keytype
56 =head2 DH and DHX additional parameters
68 =head2 DH additional domain parameters
85 =head2 DH and DHX domain parameter / key generation parameters
189 A B<DH> key can be generated using domain parameters by calling:
[all …]
A DEVP_PKEY-DSA.pod16 =head2 DSA parameters
18 The B<DSA> key type supports the FFC parameters (see
19 L<EVP_PKEY-FFC(7)/FFC parameters>).
21 =head2 DSA key generation parameters
23 The B<DSA> key type supports the FFC key generation parameters (see
24 L<EVP_PKEY-FFC(7)/FFC key generation parameters>
38 The B<DSA> domain parameters can be generated by calling:
62 A B<DSA> key can be generated using domain parameters by calling:
A DEVP_PKEY-HMAC.pod22 =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
A DEVP_SIGNATURE-DSA.pod15 The following signature parameters can be set using EVP_PKEY_CTX_set_params().
25 The settable parameters are described in L<provider-signature(7)>.
29 The following signature parameters can be retrieved using
38 The gettable parameters are described in L<provider-signature(7)>.
A DEVP_SIGNATURE-ECDSA.pod14 The following signature parameters can be set using EVP_PKEY_CTX_set_params().
24 These parameters are described in L<provider-signature(7)>.
28 The following signature parameters can be retrieved using
37 The parameters are described in L<provider-signature(7)>.
A Dprovider-keyexch.pod32 /* Key Exchange parameters */
138 OSSL_FUNC_keyexch_set_ctx_params() sets key exchange parameters associated with the
140 see L</Common Key Exchange parameters>.
144 OSSL_FUNC_keyexch_get_ctx_params() gets key exchange parameters associated with the
146 see L</Common Key Exchange parameters>.
150 describes the settable parameters, i.e. parameters that can be used with
155 array that describes the gettable parameters, i.e. parameters that can be
161 Notice that not all settable parameters are also gettable, and vice versa.
163 =head2 Common Key Exchange parameters
165 See L<OSSL_PARAM(3)> for further details on the parameters structure used by
[all …]
A DEVP_MAC-KMAC.pod25 =head2 Supported parameters
27 The general description of these parameters can be found in
30 All these parameters can be set with EVP_MAC_CTX_set_params().
68 The "xof" and "size" parameters can be set at any time before EVP_MAC_final().
98 * Setup parameters required before calling EVP_MAC_init()
99 * The parameters OSSL_MAC_PARAM_XOF and OSSL_MAC_PARAM_SIZE may also be
116 * Note: the following optional parameters can be set any time
/openssl-master/providers/common/der/
A DRSA.asn119 -- the parameters MUST be present and MUST be NULL.
25 -- parameters MUST be present and MUST be RSAES-OAEP-params.
31 -- parameters MUST be an OCTET STRING.
37 -- parameters MUST be present and MUST be RSASSA-PSS-params.
43 -- the parameters MUST be present and MUST be NULL.
56 -- When id-mgf1 is used in an AlgorithmIdentifier, the parameters

Completed in 27 milliseconds

12345678910>>...14