/openssl/ |
H A D | README-PROVIDERS.md | 31 that will be used. It is loaded automatically the first time that we try to 32 get an algorithm from a provider if no other provider has been loaded yet. 33 If another provider has already been loaded then it won't be loaded 46 compatibility reasons. This provider is **not** loaded by default. 79 automatically loaded, the null provider can be loaded instead. 87 Providers to be loaded can be specified in the OpenSSL config file. 113 Note that once you have explicitly loaded a provider into the library context 114 the default provider will no longer be automatically loaded. Therefore you will
|
H A D | README-ENGINES.md | 179 loaded ENGINE to be discoverable by application code later on using the 186 that has been loaded from the shared-library. As such, any control 187 commands supported by the loaded ENGINE could then be executed as per 250 ENGINEs explicitly loaded using user/admin provided control commands. 255 overheads from only *that* ENGINE once it has been loaded. 258 a shared-library that can be loaded by "dynamic" isn't automated in
|
/openssl/apps/lib/ |
H A D | engine_loader.c | 42 int loaded; /* 0 = key not loaded yet, 1 = key loaded */ member 121 if (ctx->loaded == 0) { in engine_load() 137 ctx->loaded = 1; in engine_load() 152 return ctx->loaded != 0; in engine_eof()
|
/openssl/doc/man3/ |
H A D | SSL_CTX_use_serverinfo.pod | 36 meaning as for L<SSL_CTX_add_custom_ext(3)>. If serverinfo is being loaded for 61 SSL_CTX_use_certificate(), the serverinfo extension will be loaded into the 63 loaded serverinfo extension data will be loaded for that certificate. To 66 each time a certificate is loaded via a call to SSL_CTX_use_certificate().
|
H A D | CTLOG_STORE_new.pod | 24 logs). The list can be loaded from one or more files and then searched by LogID 38 path instead. Both of these functions append any loaded CT logs to the 66 all CT logs in the file are successfully parsed and loaded, 0 otherwise.
|
H A D | SSL_CTX_set_ctlog_list_file.pod | 35 return 1 if the log list is successfully loaded, and 0 if an error occurs. In 36 the case of an error, the log list may have been partially loaded.
|
H A D | X509_LOOKUP_hash_dir.pod | 58 Functions return number of objects loaded from file or 0 in case of 83 they are loaded. As of OpenSSL 1.0.0, it also checks for newer CRLs 109 loaded, hash_dir lookup method checks only for certificates with 139 the number of loaded objects or 0 on error.
|
H A D | OSSL_LIB_CTX.pod | 59 In addition providers that are not loaded in the parent library context can be 60 explicitly loaded into the child library context independently from the parent 61 library context. Providers loaded independently in this way will not be mirrored 89 This can be used to associate a library context with providers that are loaded
|
H A D | OSSL_PROVIDER.pod | 106 loaded and initialized or if I<retain_fallbacks> is nonzero. 112 that are passed as the configuration of the loaded provider. The parameters 124 OSSL_PROVIDER_do_all() iterates over all loaded providers, calling 126 I<cbdata> that comes from the caller. If no other provider has been loaded
|
H A D | X509_LOOKUP.pod | 109 X509_LOOKUP_load_file_ex() passes a filename to be loaded immediately 120 certificates and CRLs are loaded on demand into the associated 127 from which containers with certificates and CRLs are loaded on demand 135 which certificates and CRLs are immediately loaded into the associated
|
H A D | CONF_modules_free.pod | 32 B<all> is set to B<0> only modules loaded from DSOs will be unloads. If
|
H A D | OSSL_LIB_CTX_set_conf_diagnostics.pod | 22 diagnostics flag can be also set when a configuration file is being loaded
|
/openssl/doc/man7/ |
H A D | ossl-guide-libraries-introduction.pod | 41 provider loaded that contains an implementation of it. OpenSSL comes with a 51 then the OpenSSL built-in "default" provider will be automatically loaded. 58 loaded for the duration of the application execution. 64 a provider is loaded, it is only loaded within the scope of a given library 67 loaded with different configuration settings. 186 needed (if other providers are loaded and offer implementations of the same 193 provider would also need to be explicitly loaded if it is required. 201 Should it be needed (if other providers are loaded and offer 214 be loaded explicitly, either in code or through OpenSSL configuration 232 be loaded explicitly, either in code or through OpenSSL configuration [all …]
|
H A D | X25519.pod | 31 L<EVP_PKEY_new_raw_private_key(3)> or loaded from a PKCS#8 private key file 37 L<EVP_PKEY_new_raw_public_key(3)> or loaded from a SubjectPublicKeyInfo
|
H A D | OSSL_PROVIDER-default.pod | 12 provider that will be used as fallback: It is loaded automatically the 14 acting on providers is called and no other provider has been loaded yet. 17 or not) then the default provider won't be loaded automatically. Therefore 19 then it must be loaded explicitly. Automatic loading of the default 22 loaded again.
|
H A D | fips_module.pod | 161 Using this mechanism you can control which config file is loaded (and hence 162 whether the FIPS module is loaded) on an application by application basis. 181 FIPS module, but it is not automatically loaded when the application starts. The 182 FIPS provider can then be loaded programmatically like this: 213 loaded, then the default provider will be automatically loaded. If you then 215 default provider loaded at the same time. It is undefined which implementation 220 Also note that in this example we have additionally loaded the "base" provider. 351 * other providers are loaded. 414 You should ensure that either the default or base provider is loaded into the 435 * provider loaded has been created called fips_libctx. [all …]
|
H A D | openssl-env.pod | 41 Specifies the directory from which dynamic engines are loaded. 51 Specifies the directory from which cryptographic providers are loaded.
|
H A D | ossl-guide-libcrypto-introduction.pod | 75 context created by the user. Only providers loaded in this library context (see 77 no provider has been loaded in this library context then the default provider 78 will be loaded as a fallback (see L<OSSL_PROVIDER-default(7)>). 253 since, assuming no other providers have been loaded, the only implementation of 255 default provider should be explicitly loaded if it is required in addition to
|
/openssl/doc/man1/ |
H A D | openssl-engine.pod.in | 64 The B<-pre> command is given to the engine before it is loaded and 65 the B<-post> command is given after the engine is loaded. 88 LIST_ADD: Whether to add a loaded ENGINE to the internal list (0=no,1=yes,2=mandatory) 92 DIR_ADD: Adds a directory from which ENGINEs can be loaded
|
/openssl/doc/designs/ |
H A D | ossl-provider-load-ex.md | 48 When the provider is already loaded an activated in the current library context, 55 Separate instances of the provider can be loaded in the separate library 58 Several instances of the same provider can be loaded in the same context using 64 Changing the loaded provider configuration at runtime is not supported. If
|
/openssl/doc/internal/man7/ |
H A D | VERSION.pod | 91 The fully loaded version number, a string composed from $config{version}, 109 The fully loaded version number ($config{full_version}) will be 120 The fully loaded version number ($config{full_version}) will be 131 The fully loaded version number ($config{full_version}) will be
|
/openssl/test/ |
H A D | provider_test.c | 312 int loaded = 0; in setup_tests() local 319 loaded = 1; in setup_tests() 326 if (!loaded) { in setup_tests()
|
/openssl/doc/internal/man3/ |
H A D | ossl_algorithm_do_all.pod | 25 I<provider> may be NULL to signify that all loaded providers will be 42 application that wants to display the loaded providers and what they
|
H A D | ossl_provider_new.pod | 53 * If the Provider is a module, the module will be loaded 65 /* Iterate over all loaded providers */ 125 The config file will be automatically loaded unless I<noconfig> is set. 136 The config file will be automatically loaded unless I<noconfig> is set. 159 was loaded, and I<prov> itself will be freed. 210 will be located and loaded, then the symbol B<OSSL_provider_init> will
|
/openssl/crypto/property/ |
H A D | README.md | 9 * Property definition is uncommon. I.e. providers will be loaded and 53 the chosen algorithm. When a provider is loaded or unloaded, this cache
|