Lines Matching refs:origin
23 as its "internal key" or "origin" (the reason for "origin" is
29 =item legacy origin
43 =item provider-native origin
60 confusing which one of the two is the origin.
95 For provider native origin keys, this doesn't require any help from
99 For legacy origin keys, this requires the associated
121 the key data that the cached keys came from is the "origin", and since
122 there are two forms of the latter, we have the "legacy origin" and the
123 "provider native origin".>
126 what form the origin has.
127 For a legacy origin, this requires that the associated
130 For a provider native origin, this requires that the associated
137 with that key are limited to the same backend as the origin key
138 (ENGINE for legacy origin keys, provider for provider side origin
150 Check if the dirty count for the internal origin key has changed since
169 Export the internal origin key to the provider, using the appropriate
172 For legacy origin keys, that's done with the help of the
175 For provider native origin keys, that's done by retrieving the key
176 data in L<OSSL_PARAM(3)> form from the origin keys, using the
184 =head2 Changing a key origin
186 It is never possible to change the origin of a key. An B<EVP_PKEY> with a legacy
187 origin will I<never> be upgraded to become an B<EVP_PKEY> with a provider
188 native origin. Instead, we have the operation cache as described above, that
192 Similarly an B<EVP_PKEY> with a provider native origin, will I<never> be
193 I<transformed> into an B<EVP_PKEY> with a legacy origin. Instead we may have a
