diff options
| author | Tomas Mraz <tomas@openssl.org> | 2021-06-09 17:04:12 +0200 |
|---|---|---|
| committer | Pauli <pauli@openssl.org> | 2021-06-11 08:52:26 +1000 |
| commit | b19fcc66d382357617744690dc3363947de2cb6f (patch) | |
| tree | 24db98bd9a3daa22305f41bf8c16aa8b01e1149e /doc | |
| parent | d475a9efcfb98fe2d207dbc56bed931ee35b74a6 (diff) | |
| download | openssl-new-b19fcc66d382357617744690dc3363947de2cb6f.tar.gz | |
Document that provider name can be a full path
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15680)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/man1/openssl.pod | 7 | ||||
| -rw-r--r-- | doc/man3/OSSL_PROVIDER.pod | 7 |
2 files changed, 12 insertions, 2 deletions
diff --git a/doc/man1/openssl.pod b/doc/man1/openssl.pod index 3b47ae9729..b6f4029a67 100644 --- a/doc/man1/openssl.pod +++ b/doc/man1/openssl.pod @@ -651,7 +651,12 @@ the PKCS#11 URI as defined in RFC 7512 should be possible to use directly: =item B<-provider> I<name> -Load and initialize the provider identified by I<name>. +Load and initialize the provider identified by I<name>. The I<name> +can be also a path to the provider module. In that case the provider name +will be the specified path and not just the provider module name. +Interpretation of relative paths is platform specific. The configured +"MODULESDIR" path, B<OPENSSL_MODULES> environment variable, or the path +specified by B<-provider-path> is prepended to relative paths. See L<provider(7)> for a more detailed description. =item B<-provider-path> I<path> diff --git a/doc/man3/OSSL_PROVIDER.pod b/doc/man3/OSSL_PROVIDER.pod index 2b014c4671..bc4cc1641e 100644 --- a/doc/man3/OSSL_PROVIDER.pod +++ b/doc/man3/OSSL_PROVIDER.pod @@ -81,7 +81,12 @@ OSSL_PROVIDER_load() loads and initializes a provider. This may simply initialize a provider that was previously added with OSSL_PROVIDER_add_builtin() and run its given initialization function, or load a provider module with the given name and run its provider -entry point, C<OSSL_provider_init>. +entry point, C<OSSL_provider_init>. The I<name> can be a path +to a provider module, in that case the provider name as returned +by OSSL_PROVIDER_get0_name() will be the path. Interpretation +of relative paths is platform dependent and they are relative +to the configured "MODULESDIR" directory or the path set in +the environment variable OPENSSL_MODULES if set. OSSL_PROVIDER_try_load() functions like OSSL_PROVIDER_load(), except that it does not disable the fallback providers if the provider cannot be |