Lines Matching refs:legacy
29 =item legacy origin
66 This is especially visible with internal legacy keys, since they can
99 For legacy origin keys, this requires the associated
122 there are two forms of the latter, we have the "legacy origin" and the
127 For a legacy origin, this requires that the associated
138 (ENGINE for legacy origin keys, provider for provider side origin
172 For legacy origin keys, that's done with the help of the
186 It is never possible to change the origin of a key. An B<EVP_PKEY> with a legacy
193 I<transformed> into an B<EVP_PKEY> with a legacy origin. Instead we may have a
194 cached copy of the provider key in legacy form. Once the cached copy is created
196 the cached legacy copy. Similarly changes made to the cached legacy copy are not