| /openssl/include/crypto/ |
| H A D | riscv_arch.def | 13 * Each RISC-V capability ends up encoded as a single set bit in an array of
14 * words. When specifying a new capability, write a new RISCV_DEFINE_CAP
16 * second argument as the index in the array where the capability will be stored
18 * capability.
23 * When there is no hwprobe key/value pair for a capability, the key is set to -1
25 * the value is set to 0 and the corresponding capability would not be enabled.
|
| /openssl/doc/man7/ |
| H A D | OSSL_STORE-winstore.pod | 43 The documented capability to override EKU
47 The undocumented capability to add name constraints
51 The undocumented capability to override the certificate expiry date
|
| H A D | provider-base.pod | 122 int provider_get_capabilities(void *provctx, const char *capability,
426 L<OSSL_PARAM(3)>s should provide details about the capability with the name given
427 in the I<capability> argument relevant for the provider context I<provctx>. If a
429 callback multiple times (one for each capability). Capabilities can be useful for
554 The "TLS-GROUP" capability can be queried by libssl to discover the list of
647 The "TLS-SIGALG" capability can be queried by libssl to discover the list of
|
| /openssl/doc/man3/ |
| H A D | OPENSSL_ia32cap.pod | 14 extensions are denoted by individual bits in capability vector returned
69 enable XMM registers. Historically address of the capability vector copy
71 anymore. Now the only way to affect the capability detection is to set
86 The capability vector is further extended with EBX value returned by
121 To control this extended capability word use C<:> as delimiter when
|
| H A D | BIO_s_dgram_pair.pod | 132 Each half of a BIO datagram pair can have capability flags set on it which
134 and whether they will be provided by the writer. These capability flags should
137 opposite BIO. If necessary, the capability value previously set can be retrieved
172 B<BIO_DGRAM_CAP_HANDLES_DST_ADDR> capability, the operation fails. Thus,
173 capability negotiation is mandatory.
183 capability), the operation fails.
188 that half of the BIO datagram pair. However, these capability flags do not
|
| H A D | OSSL_PROVIDER.pod | 59 const char *capability,
170 supported by the provider specified in I<prov> with the capability name
171 I<capability>. For each capability of that name supported by the provider it
173 capability. It will also pass back the argument I<arg>. For more details about
|
| H A D | SSL_CTX_set_split_send_fragment.pod | 36 capability could be utilised to parallelise the processing of a single
40 capability is known as "pipelining" within OpenSSL.
42 In order to benefit from the pipelining capability. You need to have an engine
44 AES128-SHA based ciphers that have this capability. However, these are for
|
| H A D | OpenSSL_version.pod | 159 This is the current setting of the cpu capability flags. It is usually
218 This is the current setting of the cpu capability flags. It is usually
|
| H A D | OPENSSL_riscvcap.pod | 33 zba/zbb/zbs would not be implied in the capability vector.
|
| H A D | RAND_add.pod | 72 and it takes effect immediately. This capability only applies to the default
|
| H A D | OPENSSL_s390xcap.pod | 20 application. After initialization, the capability vector is ANDed bitwise
|
| H A D | SSL_CTX_set_tlsext_use_srtp.pod | 26 capability may be used as part of an implementation that conforms to RFC5763.
|
| H A D | d2i_X509.pod | 444 However using the "reuse" capability for other purposes is B<strongly
542 B<I<TYPE>> structure or NULL if an error occurs. If the "reuse" capability has
|
| H A D | X509_LOOKUP_hash_dir.pod | 131 loader, and therefore depends on the loader's capability.
|
| H A D | SSL_CTX_set0_CA_list.pod | 57 if the list is large. This optional capability was introduced as part of TLSv1.3
|
| /openssl/crypto/ |
| H A D | provider.c | 119 const char *capability, in OSSL_PROVIDER_get_capabilities() argument
123 return ossl_provider_get_capabilities(prov, capability, cb, arg); in OSSL_PROVIDER_get_capabilities()
|
| H A D | provider_core.c | 1786 const char *capability, in ossl_provider_get_capabilities() argument
1796 capability == NULL ? "none" : capability); in ossl_provider_get_capabilities()
1799 return prov->get_capabilities(prov->provctx, capability, cb, arg); in ossl_provider_get_capabilities()
|
| /openssl/test/ |
| H A D | filterprov.c | 70 static int filter_get_capabilities(void *provctx, const char *capability, in filter_get_capabilities() argument
75 return OSSL_PROVIDER_get_capabilities(globs->deflt, capability, cb, arg); in filter_get_capabilities()
|
| H A D | README-external.md | 5 This capability is considered a developer option and does not work on all
|
| /openssl/providers/common/ |
| H A D | capabilities.c | 223 int ossl_prov_get_capabilities(void *provctx, const char *capability, in ossl_prov_get_capabilities() argument
226 if (OPENSSL_strcasecmp(capability, "TLS-GROUP") == 0) in ossl_prov_get_capabilities()
|
| /openssl/include/openssl/ |
| H A D | provider.h | 43 const char *capability,
|
| /openssl/include/internal/ |
| H A D | provider.h | 86 const char *capability,
|
| /openssl/doc/internal/man3/ |
| H A D | ossl_provider_new.pod | 83 const char *capability,
275 if the provider has one. It provides the name of the I<capability> and a
276 callback I<cb> parameter to call for each capability that has a matching name in
277 the provider. The callback gets passed OSSL_PARAM details about the capability as
375 support the requested capability then 0 is returned.
|
| /openssl/ |
| H A D | NOTES-VALGRIND.md | 48 processor, and use it to its fullest capability. This variable can be
|
| H A D | NOTES-NONSTOP.md | 45 The PUT model is incompatible with the QUIC capability. This capability should
|
