Home
last modified time | relevance | path

Searched refs:algorithm (Results 1 – 25 of 415) sorted by relevance

12345678910>>...17

/openssl/test/recipes/
H A D15-test_gendhparam.t19 algorithm => 'DHX',
25 algorithm => 'DH',
31 algorithm => 'DHX',
37 algorithm => 'DHX',
43 algorithm => 'DHX',
49 algorithm => 'DH',
55 algorithm => 'DH',
61 algorithm => 'DH',
67 algorithm => 'DH',
73 algorithm => 'DH',
[all …]
/openssl/crypto/asn1/
H A Dx_algor.c40 ASN1_OBJECT_free(alg->algorithm);
41 alg->algorithm = aobj;
76 *paobj = algor->algorithm; in X509_ALGOR_get0()
100 rv = OBJ_cmp(a->algorithm, b->algorithm); in X509_ALGOR_cmp()
113 if (dest->algorithm) in X509_ALGOR_copy()
114 ASN1_OBJECT_free(dest->algorithm); in X509_ALGOR_copy()
115 dest->algorithm = NULL; in X509_ALGOR_copy()
121 if (src->algorithm) in X509_ALGOR_copy()
122 if ((dest->algorithm = OBJ_dup(src->algorithm)) == NULL) in X509_ALGOR_copy()
163 md = EVP_get_digestbyobj(alg->algorithm); in ossl_x509_algor_get_md()
[all …]
/openssl/doc/man1/
H A Dopenssl-genpkey.pod.in24 [B<-algorithm> I<alg>]
80 =item B<-algorithm> I<alg>
104 B<openssl> B<genpkey> -algorithm XXX -help
333 The B<algorithm> option must be B<"DH">.
338 The B<algorithm> option must be B<"DHX">.
343 The B<algorithm> option must be B<"DHX">.
349 The B<algorithm> option must be B<"DH">.
415 openssl genpkey -algorithm RSA -out key.pem
423 openssl genpkey -algorithm RSA -out key.pem \
492 openssl genpkey -algorithm EC -out eckey.pem \
[all …]
H A Dopenssl-speed.pod.in33 [I<algorithm> ...]
61 Use the specified cipher or message digest algorithm via the EVP interface.
84 Time the HMAC algorithm using the specified message digest.
88 Time the CMAC algorithm using the specified cipher e.g.
114 is only effective if RSA algorithm is specified to test.
136 Runs the speed command in testmode. Runs only 1 iteration of each algorithm test
146 =item I<algorithm> ...
148 If any I<algorithm> is given, then those algorithms are tested, otherwise a
155 The I<algorithm> can be selected only from a pre-compiled subset of things
157 or cipher algorithm supported by OpenSSL use the C<-evp> option.
H A Dopenssl-pkeyutl.pod.in6 openssl-pkeyutl - public key algorithm command
14 [B<-digest> I<algorithm>]
34 [B<-kdf> I<algorithm>]
49 operations using any supported algorithm.
69 which is not hashed by any message digest algorithm.
73 the default digest algorithm is SHA-256. For SM2, it is SM3.
81 =item B<-digest> I<algorithm>
219 =item B<-kdf> I<algorithm>
226 for the supported string parameters of each algorithm.
297 The RSA algorithm generally supports the encrypt, decrypt, sign,
[all …]
H A Dopenssl-mac.pod.in50 Used by CMAC and GMAC to specify the cipher algorithm.
58 The string length must conform to any restrictions of the MAC algorithm.
63 Passes options to the MAC algorithm.
74 The string length must conform to any restrictions of the MAC algorithm.
75 A key must be specified for every MAC algorithm.
80 The key length must conform to any restrictions of the MAC algorithm.
81 A key must be specified for every MAC algorithm.
116 Specifies the name of a supported MAC algorithm which will be used.
/openssl/doc/man3/
H A DEVP_PBE_CipherInit.pod35 I<pass> of length I<passlen>. The PBE algorithm type and parameters are extracted
39 I<libctx> and property query I<propq> to select appropriate algorithm
42 =head2 PBE algorithm search
46 1. An algorithm type I<type> which can be:
52 EVP_PBE_TYPE_OUTER - A PBE algorithm
64 2. A I<pbe_nid> which can represent the algorithm identifier with parameters e.g.
65 B<NID_pbeWithSHA1AndRC2_CBC> or an algorithm class e.g. B<NID_pbes2>.
67 They return the algorithm's cipher ID I<pcnid>, digest ID I<pmnid> and a key
68 generation function for the algorithm I<pkeygen>. EVP_PBE_CipherInit_ex() also
75 =head2 PBE algorithm add
[all …]
H A DOSSL_ALGORITHM.pod5 OSSL_ALGORITHM - OpenSSL Core type to define a fetchable algorithm
22 algorithm that a L<provider(7)> provides. Arrays of this type are returned
41 L<EVP_MD_fetch(3)>, etc) to find the desired algorithm.
44 fetched multiple ways. For example, the RSA algorithm has the following
72 The OpenSSL libraries use the first of the algorithm names as the main
73 or canonical name, on a per algorithm implementation basis.
82 algorithm implementation, and is used by the appropriate fetching
85 case multiple implementations of the same algorithm are available.
93 functions of a particular algorithm implementation.
97 A string with a short human-readable description of the algorithm.
[all …]
H A DPKCS12_pack_p7encdata.pod23 type from the set of safeBags I<bags>. The algorithm ID in I<pbe_nid> can be
24 a PKCS#12 or PKCS#5 password based encryption algorithm, or a cipher algorithm.
25 If a cipher algorithm is passed, the PKCS#5 PBES2 algorithm will be used with
32 algorithm implementation.
H A DEVP_PKEY_CTX_set_rsa_pss_keygen_md.pod10 - EVP_PKEY RSA-PSS algorithm support functions
55 they have exactly the same meaning as for the RSA algorithm.
64 EVP_PKEY_CTX_set_rsa_pss_keygen_md() restricts the digest algorithm the
67 passes the algorithm by name rather than by B<EVP_MD>.
69 EVP_PKEY_CTX_set_rsa_pss_keygen_mgf1_md() restricts the MGF1 algorithm the
72 passes the algorithm by name rather than by B<EVP_MD>.
79 A context for the B<RSA-PSS> algorithm can be obtained by calling:
87 the public key algorithm.
H A DEVP_PKEY_CTX_new.pod8 - public key algorithm context functions
28 The EVP_PKEY_CTX_new() function allocates public key algorithm context using
31 The EVP_PKEY_CTX_new_id() function allocates public key algorithm context
34 The EVP_PKEY_CTX_new_from_name() function allocates a public key algorithm
41 The EVP_PKEY_CTX_new_from_pkey() function allocates a public key algorithm
43 algorithm specified by I<pkey> and the property query I<propquery>. None of the
64 The B<EVP_PKEY_CTX> structure is an opaque public key algorithm context used
72 as "algorithm" in most cases, allowing either term to be used
74 I<algorithm> of the operations that use the keys are not the same,
H A DEVP_PKEY_verify_recover.pod7 - recover signature using a public key algorithm
24 EVP_PKEY_verify_recover_init() initializes a public key algorithm context
25 I<ctx> for signing using the algorithm given when the context was created
26 using L<EVP_PKEY_CTX_new(3)> or variants thereof. The algorithm is used to
37 Depending on what algorithm was fetched, certain details revolving around the
60 After the call to EVP_PKEY_verify_recover_init() algorithm specific control
64 After the call to EVP_PKEY_verify_recover_init_ex2(), algorithm specific control
65 operations may not be needed if the chosen algorithm implies that those controls
75 indicates the operation is not supported by the public key algorithm.
H A DEVP_ASYM_CIPHER_free.pod10 - Functions to manage EVP_ASYM_CIPHER algorithm objects
16 EVP_ASYM_CIPHER *EVP_ASYM_CIPHER_fetch(OSSL_LIB_CTX *ctx, const char *algorithm,
37 B<algorithm> from any provider offering it, within the criteria given
39 L<OSSL_LIB_CTX(3)>). The algorithm will be one offering functions for performing
54 algorithm that's identifiable with I<name>, otherwise 0.
64 EVP_ASYM_CIPHER_get0_name() returns the algorithm name from the provided
67 algorithm definition is returned. Ownership of the returned string is retained
79 parameters that can be retrieved or set by a key encryption algorithm using
H A DEVP_KEM_free.pod9 - Functions to manage EVP_KEM algorithm objects
15 EVP_KEM *EVP_KEM_fetch(OSSL_LIB_CTX *ctx, const char *algorithm,
32 EVP_KEM_fetch() fetches the implementation for the given B<algorithm> from any
34 scope of the given library context B<ctx> (see L<OSSL_LIB_CTX(3)>). The algorithm
49 algorithm that's identifiable with I<name>, otherwise 0.
58 EVP_KEM_get0_name() returns the algorithm name from the provided
61 algorithm definition is returned. Ownership of the returned string is retained
73 parameters that can be retrieved or set by a key encapsulation algorithm using
H A DEVP_SIGNATURE.pod11 - Functions to manage EVP_SIGNATURE algorithm objects
19 EVP_SIGNATURE *EVP_SIGNATURE_fetch(OSSL_LIB_CTX *ctx, const char *algorithm,
41 B<algorithm> from any provider offering it, within the criteria given
43 The algorithm will be one offering functions for performing signature related
58 algorithm that's identifiable with I<name>, otherwise 0.
68 EVP_SIGNATURE_get0_name() returns the algorithm name from the provided
71 algorithm definition is returned. Ownership of the returned string is retained
83 parameters that can be retrieved or set by a signature algorithm using
H A DX509_digest.pod44 using the same hash algorithm as in its signature, if the digest
45 is an integral part of the certificate signature algorithm identifier.
46 Otherwise, a fallback hash algorithm is determined as follows:
47 SHA512 if the signature algorithm is ED25519,
50 Unless I<md_used> is NULL, the hash algorithm used is provided
53 the I<*md_is_fallback> is set to 1 if the hash algorithm used is a fallback,
H A DEVP_KEYEXCH_free.pod9 - Functions to manage EVP_KEYEXCH algorithm objects
15 EVP_KEYEXCH *EVP_KEYEXCH_fetch(OSSL_LIB_CTX *ctx, const char *algorithm,
35 I<algorithm> from any provider offering it, within the criteria given
53 algorithm that's identifiable with I<name>.
55 EVP_KEYEXCH_get0_name() returns the algorithm name from the provided
58 algorithm definition is returned. Ownership of the returned string is retained
75 parameters that can be retrieved or set by a key exchange algorithm using
/openssl/doc/man7/
H A Dossl-guide-libcrypto-introduction.pod25 referred to in OpenSSL as "algorithms". Each algorithm may have multiple
84 specific documentation for information on the algorithm implementations
97 The property query string used to guide selection of the algorithm
110 OpenSSL has a number of functions that return an algorithm object with no
156 Fetch a message digest/hashing algorithm implementation.
160 Fetch a symmetric cipher algorithm implementation.
164 Fetch a Key Derivation Function (KDF) algorithm implementation.
168 Fetch a Message Authentication Code (MAC) algorithm implementation.
172 Fetch a Key Encapsulation Mechanism (KEM) algorithm implementation
186 Fetch a Pseudo Random Number Generator (PRNG) algorithm implementation.
[all …]
H A Dopenssl-glossary.pod17 implementation for any given algorithm available for use.
34 the algorithm implementations in the Base Provider are also available in the
48 An OpenSSL Provider that contains the most common OpenSSL algorithm
50 the algorithm implementations in the Base Provider are also available in the
75 where a function call is made to obtain an algorithm object representing an
80 Fetching is the process of looking through the available algorithm
90 An OpenSSL Provider that contains OpenSSL algorithm implementations that have
101 criteria the first time the algorithm is used.
127 An OpenSSL Provider that contains no algorithm implementations. This can be
175 A property is a way of classifying and selecting algorithm implementations.
[all …]
H A DEVP_PKEY-SM2.pod10 The B<SM2> algorithm was first defined by the Chinese national standard GM/T
12 an elliptic curve based algorithm. The current implementation in OpenSSL supports
15 When doing the B<SM2> signature algorithm, it requires a distinguishing identifier
41 Note that the SM2 algorithm requires the presence of the public key for signatures,
59 Currently, the only valid algorithm name is B<sm2>.
67 a message with the SM2 signature algorithm and the SM3 hash algorithm:
H A DRSA-PSS.pod5 RSA-PSS - EVP_PKEY RSA-PSS algorithm support
10 algorithm which only supports signing, verification and key generation
15 This algorithm shares several control operations with the B<RSA> algorithm
20 Signing and verification is similar to the B<RSA> algorithm except the
H A DEVP_KDF-PBKDF1.pod12 The EVP_KDF-PBKDF1 algorithm implements the PBKDF1 password-based key
45 A typical application of this algorithm is to derive keying material for an
46 encryption algorithm from a password in the "pass", a salt in "salt",
49 Increasing the "iter" parameter slows down the algorithm which makes it
56 The legacy provider needs to be available in order to access this algorithm.
H A DEVP_KDF-PKCS12KDF.pod12 The EVP_KDF-PKCS12KDF algorithm implements the PKCS#12 password-based key
49 This algorithm is not available in the FIPS provider as it is not FIPS
52 A typical application of this algorithm is to derive keying material for an
53 encryption algorithm from a password in the "pass", a salt in "salt",
56 Increasing the "iter" parameter slows down the algorithm which makes it
/openssl/doc/designs/
H A Dfetching-composite-algorithms.md55 Because it's not immediately obvious from a composite algorithm name what
57 explicitly fetched implementation of a composite algorithm requires that
59 each algorithm.
89 with the fetched algorithm:
94 - Check if the fetched algorithm name matches the name returned by the
116 ### What is a composite algorithm?
118 A composite algorithm is an algorithm that's composed of more than one other
119 algorithm. In OpenSSL parlance with a focus on signatures, they have been
129 AlgorithmIdentifier is an ASN.1 structure that defines an algorithm as an
130 OID, along with parameters that should be passed to that algorithm.
[all …]
/openssl/crypto/ocsp/
H A Docsp_lib.c57 ASN1_OBJECT_free(alg->algorithm); in OCSP_cert_id_new()
62 if ((alg->algorithm = OBJ_nid2obj(nid)) == NULL) in OCSP_cert_id_new()
95 ret = OBJ_cmp(a->hashAlgorithm.algorithm, b->hashAlgorithm.algorithm); in OCSP_id_issuer_cmp()

Completed in 44 milliseconds

12345678910>>...17