Searched refs:structure (Results 276 – 300 of 382) sorted by relevance
1...<<111213141516
/openssl/doc/internal/man3/ |
H A D | evp_pkey_export_to_provider.pod | 40 evp_pkey_get_legacy() obtains and returns a legacy key structure. If the
|
H A D | ossl_cmp_mock_srv_new.pod | 92 ossl_cmp_mock_srv() returns a B<OSSL_CMP_SRV_CTX> structure on success,
|
/openssl/doc/man3/ |
H A D | EVP_PBE_CipherInit.pod | 84 together form an B<X509_ALGOR> and can often be extracted directly from this structure.
|
H A D | PEM_bytes_read_bio.pod | 5 PEM_bytes_read_bio, PEM_bytes_read_bio_secmem - read a PEM-encoded data structure from a BIO
|
H A D | SSL_CONF_cmd.pod | 205 structure is associated with B<ctx>. 261 structure is set or SSL_use_certificate_file() with filetype PEM if an 262 B<SSL> structure is set. This option is only supported if certificate 317 structure is associated with B<ctx>. 330 structure is set or SSL_use_certificate_file() with filetype PEM if an B<SSL> 331 structure is set. This option is only supported if certificate operations 658 The value is a string without any specific structure.
|
H A D | OCSP_resp_find_status.pod | 74 OCSP_resp_get0() returns the B<OCSP_SINGLERESP> structure in I<bs> corresponding 150 OCSP_resp_get0() returns a pointer to an B<OCSP_SINGLERESP> structure or
|
H A D | EVP_EncryptInit.pod | 253 The B<EVP_CIPHER> type is a structure for cipher method implementation. 269 Increments the reference count for an B<EVP_CIPHER> structure. 273 Decrements the reference count for the fetched B<EVP_CIPHER> structure. 274 If the reference count drops to 0 then the structure is freed. 468 an B<ASN1_OBJECT> structure respectively. 495 structure. The actual NID value is an internal value which may not have a 521 B<EVP_CIPHER_CTX> structure. The constant B<EVP_MAX_KEY_LENGTH> is the maximum 549 B<EVP_CIPHER_CTX> structure. The constant B<EVP_MAX_BLOCK_LENGTH> is also the 592 Returns the B<EVP_CIPHER> structure when passed an B<EVP_CIPHER_CTX> structure. 1320 return an B<EVP_CIPHER> structure or NULL on error. [all …]
|
H A D | ADMISSIONS.pod | 163 structure and must not be freed.
|
H A D | EC_GROUP_new.pod | 119 and freeing the structure in a loop). 161 The EC_builtin_curve structure is defined as follows:
|
H A D | OSSL_trace_set_channel.pod | 163 More precisely, both reference counts in the ENGINE structure will be 207 Traces decrementing certain ASN.1 structure references.
|
H A D | ASN1_STRING_print_ex.pod | 20 These functions output an B<ASN1_STRING> structure. B<ASN1_STRING> is used to
|
/openssl/doc/designs/ |
H A D | ossl-provider-load-ex.md | 76 2. We probably should remove the `INFOPAIR` structure and use the `OSSL_PARAM`
|
/openssl/doc/man1/ |
H A D | openssl-ca.pod.in | 235 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or 236 YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In 243 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or 244 YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In 376 YYMMDDHHMMSSZ format (the same as an ASN1 UTCTime structure) or 377 YYYYMMDDHHMMSSZ format (the same as an ASN1 GeneralizedTime structure). 660 Note: these examples assume that the directory structure this command
|
H A D | openssl-dsaparam.pod.in | 52 This is compatible with RFC 2459 B<DSS-Parms> structure.
|
H A D | openssl-sess_id.pod.in | 24 structure and optionally prints out SSL session details (for example
|
/openssl/doc/man7/ |
H A D | provider-mac.pod | 94 structure for holding context information during a mac operation. 131 See L<OSSL_PARAM(3)> for further details on the parameters structure used by
|
H A D | proxy-certificates.pod | 155 a data structure that is shared between your application code and the 291 * in the YOUR_RIGHTS structure pointed at by the
|
H A D | provider-cipher.pod | 113 structure for holding context information during a cipher operation. 184 See L<OSSL_PARAM(3)> for further details on the parameters structure used by
|
H A D | provider-kem.pod | 115 structure for holding context information during an asymmetric kem operation. 185 See L<OSSL_PARAM(3)> for further details on the parameters structure used by
|
H A D | provider-keyexch.pod | 94 structure for holding context information during a key exchange operation. 164 See L<OSSL_PARAM(3)> for further details on the parameters structure used by
|
/openssl/ |
H A D | CHANGES.md | 3419 ASN1_STRING structure. 5588 an already created structure. 6237 RAND_METHOD structure. 7530 structure. 10923 structure. 12093 - hide BN_BLINDING structure 12364 structure of type "other". 14531 ENGINE structure. 16950 in the X509_STORE_CTX structure. 18322 PKCS12 structure. [all …]
|
/openssl/doc/designs/quic-design/ |
H A D | dgram-api.md | 44 - We ensure the extensibility of our `BIO_MSG` structure in a way that preserves 49 be added to the end of the structure. 140 - `flags` in the `BIO_MSG` structure provides per-message flags to 187 an equivalent structure. The former has the advantage that we can just pass the 203 for OS-provided structures, or our own independent structure
|
H A D | record-layer.md | 74 A METHOD based approach is simply a structure containing function pointers. It 171 the record layer. The internal structure details of an `OSSL_RECORD_LAYER` are 174 `OSSL_RECORD_METHOD`s all use a common `OSSL_RECORD_LAYER` structure. However 175 the QUIC-TLS implementation is likely to use a different structure layout. 178 `OSSL_RECORD_TEMPLATE` structure when writing. Libssl will construct a set of
|
/openssl/doc/internal/man7/ |
H A D | DERlib.pod | 42 C<end>. As an example, we can look at the DSA signature structure,
|
/openssl/crypto/engine/ |
H A D | README.md | 83 have our RSA structure pointing its RSA_METHOD pointer to the software 95 provided EVP_CIPHER structure represents. Under normal circumstances, that 98 EVP_CIPHER_CTX context, and the EVP_CIPHER structure is left hooked into the
|
Completed in 85 milliseconds
1...<<111213141516