Lines Matching full:provider

4 Currently any provider run-time activation requires the presence of the
6 provider will be activated with some default settings, that may or may not
13 provider (where different applications may use different devices with different
15 also usable for FIPS provider.
24 intended to configure the provider at load time.
27 provider can be initialized from the config file where the values are
28 represented as strings and provider init function has to deal with it.
38 provider <https://github.com/latchset/pkcs11-provider> also provides a set of
42 1. Configure a provider in the config file, activate on demand
43 2. Load/activate a provider run-time with parameters
48 When the provider is already loaded an activated in the current library context,
49 the `OSSL_PROVIDER_load_ex` call simply returns the active provider and the
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
59 different section names, module names (e.g. via symlinks) and provider names.
60 But unless the provider supports some configuration options, the algorithms in
61 this case will have the same `provider` property and the result of fetching is
64 Changing the loaded provider configuration at runtime is not supported. If
65 it is necessary, the provider needs to be unloaded using `OSSL_PROVIDER_unload`
72    of a particular provider. Having it, the application will be able to combine