Home
last modified time | relevance | path

Searched refs:implementation (Results 1 – 25 of 243) sorted by relevance

12345678910

/openssl-master/doc/man3/
A DEVP_CIPHER_meth_new.pod76 implementation.
109 implementation.
118 Set this to have the implementation's ctrl() function called with
124 is left to the implementation.
136 Making a key with random content is left to the implementation.
143 Set this to have the implementation's ctrl() function called with
146 implementation specific data block has been copied.
149 The implementation specific data block is reached with
160 bytes for this implementation.
171 This indicates that the implementation takes care of everything,
[all …]
A DOSSL_ENCODER_CTX_new_for_pkey.pod50 L<EVP_KEYMGMT(3)> implementation associated with I<pkey> to build a list of
56 If no suitable encoder implementation is found,
60 the B<OSSL_ENCODER_CTX> and missing encoder implementation, and allows it to
63 OSSL_ENCODER_CTX_set_cipher() tells the implementation what cipher
66 implementation dependent. The implementation may implement the cipher
68 it. If the implementation supports fetching the cipher, then it may
73 OSSL_ENCODER_CTX_set_passphrase() gives the implementation a
80 implementation can use to prompt for a pass phrase, giving the caller the
A DEC_GFp_simple_method.pod32 implementation method must be provided. The functions described here all return a const pointer to …
33 …THOD> structure that can be passed to EC_GROUP_NEW. It is important that the correct implementation
36 For F2^m curves there is only one implementation choice, i.e. EC_GF2_simple_method.
38 For Fp curves the lowest common denominator implementation is the EC_GFp_simple_method implementati…
41 offers an implementation optimised for use with NIST recommended curves (NIST curves are available …
A DEVP_KDF.pod68 B<EVP_KDF> is a type that holds the implementation of a KDF.
72 =head2 Algorithm implementation fetching
74 EVP_KDF_fetch() fetches an implementation of a KDF I<algorithm>, given
111 EVP_KDF_get_params() retrieves details about the implementation
132 defined by the implementation.
162 EVP_KDF_is_a() returns 1 if I<kdf> is an implementation of an
182 the I<kdf> implementation.
200 The default value, if any, is implementation dependent.
208 The default value, if any, is implementation dependent.
239 The default value, if any, is implementation dependent.
[all …]
A DOSSL_ENCODER.pod71 OSSL_ENCODER_is_a() checks if I<encoder> is an implementation of an
78 I<loader> implementation.
86 implementation method and I<arg> as arguments.
93 implementation doesn't recognise should be ignored.
98 implementation represented by an OSSL_ENCODER object, or NULL on
115 implementation for the given I<encoder>. Note that the I<encoder> may have
A DEVP_KEYEXCH_free.pod34 EVP_KEYEXCH_fetch() fetches the key exchange implementation for the given
52 EVP_KEYEXCH_is_a() checks if I<exchange> is an implementation of an
56 implementation for the given I<exchange>. Note that the I<exchange> may have
66 the I<keyexch> implementation.
70 of the implementations, calls I<fn> with the implementation method and
A DEVP_KEYMGMT.pod67 implementation.
69 EVP_KEYMGMT_is_a() checks if I<keymgmt> is an implementation of an
73 implementation for the given I<keymgmt>. Note that the I<keymgmt> may have
83 of the I<keymgmt> implementation.
87 of the implementations, calls I<fn> with the implementation method and
109 implementation represented by an EVP_KEYMGMT object, or NULL on
A DEVP_ASYM_CIPHER_free.pod36 EVP_ASYM_CIPHER_fetch() fetches the implementation for the given
53 EVP_ASYM_CIPHER_is_a() returns 1 if I<cipher> is an implementation of an
61 the implementations, calls the given function I<fn> with the implementation
65 implementation for the given I<cipher>. Note that the I<cipher> may have
75 discretion of the I<cipher> implementation.
/openssl-master/doc/man7/
A DEVP_MD-SHA1.pod5 EVP_MD-SHA1 - The SHA1 EVP_MD implementation
13 This implementation is available with the FIPS provider as well as the
18 This implementation supports the common gettable parameters described
23 This implementation supports the following L<OSSL_PARAM(3)> entries,
35 The digest implementation should calculate the complete digest as per RFC6101
A Dprovider-encoder.pod59 The ENCODER implementation may be part of a chain, where data is
61 implementation to encode an object to DER (that object is assumed to
126 The name of an implementation should match the type of object it handles.
136 This property is used to specify what type of output the implementation
153 An implementation with that output type outputs PEM formatted data.
157 An implementation with that output type outputs DER formatted data.
161 An implementation with that output type outputs MSBLOB formatted data.
165 An implementation with that output type outputs PVK formatted data.
262 If this name is invalid for the encoding implementation, the
263 implementation should refuse to perform the encoding, i.e.
[all …]
A DEVP_MD-MD5-SHA1.pod5 EVP_MD-MD5-SHA1 - The MD5-SHA1 EVP_MD implementation
15 This implementation is only available with the default provider, and is
20 This implementation supports the common gettable parameters described
25 This implementation supports the following L<OSSL_PARAM(3)> entries,
37 The digest implementation should calculate the complete digest as per RFC6101
A DEVP_MD-MDC2.pod5 EVP_MD-MDC2 - The MDC2 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
23 This implementation supports the following L<OSSL_PARAM(3)> entries,
A Dprovider-decoder.pod59 The DECODER implementation may be part of a chain, where data is
61 implementation to decode an object from PEM to DER, and another one
108 The name of an implementation should match the target type of object
109 it decodes. For example, an implementation that decodes an RSA key
110 should be named "RSA". Likewise, an implementation that decodes DER data
130 An implementation with that input type decodes PEM formatted data.
134 An implementation with that input type decodes DER formatted data.
138 An implementation with that input type decodes MSBLOB formatted data.
142 An implementation with that input type decodes PVK formatted data.
244 another decoder implementation that can decode it into something.
[all …]
A DEVP_MD-MD2.pod5 EVP_MD-MD2 - The MD2 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
A DEVP_MD-MD4.pod5 EVP_MD-MD4 - The MD4 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
A DEVP_MD-MD5.pod5 EVP_MD-MD5 - The MD5 EVP_MD implementation
13 This implementation is only available with the default provider, and is
18 This implementation supports the common gettable parameters described
A DEVP_MD-WHIRLPOOL.pod5 EVP_MD-WHIRLPOOL - The WHIRLPOOL EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
18 This implementation supports the common gettable parameters described
A DEVP_MD-RIPEMD160.pod5 EVP_MD-RIPEMD160 - The RIPEMD160 EVP_MD implementation
13 This implementation is only available with the legacy provider, and is
19 This implementation supports the common gettable parameters described
A DEVP_MAC-Poly1305.pod5 EVP_MAC-Poly1305 - The Poly1305 EVP_MAC implementation
13 This implementation is identified with this name and properties, to be
54 The OpenSSL implementation of the Poly 1305 MAC corresponds to RFC 7539.
57 RFC 8439 applies equally to the OpenSSL implementation.
A DEVP_MD-BLAKE2.pod5 EVP_MD-BLAKE2 - The BLAKE2 EVP_MD implementation
13 This implementation is only available with the default provider, and
30 This implementation supports the common gettable parameters described
A Dcrypto.pod29 a "default" implementation suitable for general use, and a "fips" implementation
49 provider loaded that contains an implementation of it. OpenSSL comes with a
105 the implementation that will be used.
158 implementation.
176 L<EVP_CipherInit_ex(3)>, the actual implementation to be used is
194 Fetch the operation type implementation from any provider given a library
198 provider of the L<EVP_PKEY(3)>'s L<EVP_KEYMGMT(3)> implementation, try to
225 Fetch any available implementation of AES-128-CBC in the default context:
253 implementation of WHIRLPOOL from it:
403 * implementation (second NULL parameter). Any SHA256 implementation will
[all …]
A Dprovider-object.pod57 implementation where the object originated (let's call it X) and its target
58 implementation (let's call it Y):
64 I<An object loading function in the target implementation>
66 The target implementation (Y) may have a function that can take an I<object
67 reference>. This can only be used if the target implementation is from the
70 The exact target implementation to use is determined from the I<object type>
79 I<An object exporter in the originating implementation>
81 The originating implementation (X) may have an exporter function. This
83 that can then be imported by the target implementation's imported function.
85 This can be used when it's not possible to fetch the target implementation
A DEVP_MD-SHA2.pod5 EVP_MD-SHA2 - The SHA2 EVP_MD implementation
13 This implementation includes the following varieties:
61 This implementation supports the common gettable parameters described
A DEVP_MAC-HMAC.pod5 EVP_MAC-HMAC - The HMAC EVP_MAC implementation
11 This implementation uses EVP_MD functions to get access to the underlying
16 This implementation is identified with this name and properties, to be
51 A flag to set the MAC digest to not initialise the implementation
A DEVP_MD-SHAKE.pod14 implementation (see L<EVP_MAC-KMAC(7)>).
18 This implementation is only available with the default provider, and
43 This implementation supports the common gettable parameters described

Completed in 27 milliseconds

12345678910