Lines Matching refs:provider
24 explained further down, in L</Export cache for provider operations>),
43 =item provider-native origin
46 key data (see L<provider-keymgmt(7)>). The internal key in the
47 B<EVP_PKEY> is a pointer to that key data held by the provider, and
69 internal key is a provider key then the return value from functions such as
71 copy are not reflected back in the provider key.
73 Internal provider native keys are also possible to be modified, if the
93 in L</Export cache for provider operations>.
95 For provider native origin keys, this doesn't require any help from
104 =head2 Export cache for provider operations
107 diverse providers, potentially others than the provider of the
111 provider that is going to perform the operation (this also implies
112 that every provider that implements a key pair based operation must
118 provider side key data and the associated L<EVP_KEYMGMT(3)>.
123 "provider native origin".>
130 For a provider native origin, this requires that the associated
132 (see L<provider-keymgmt(7)>).
138 (ENGINE for legacy origin keys, provider for provider side origin
159 L<EVP_KEYMGMT(3)> that's the same provider that an export is to be
160 made to (which is the provider that's going to perform an operation
169 Export the internal origin key to the provider, using the appropriate
175 For provider native origin keys, that's done by retrieving the key
179 the provider that's to perform the operation, using its
187 origin will I<never> be upgraded to become an B<EVP_PKEY> with a provider
192 Similarly an B<EVP_PKEY> with a provider native origin, will I<never> be
194 cached copy of the provider key in legacy form. Once the cached copy is created
195 it is never updated. Changes made to the provider key are not reflected back in
197 reflected back in the provider key.
201 L<provider-keymgmt(7)>