Lines Matching refs:dynamic

29 In addition, dynamic binding to external ENGINE implementations is now
30 provided by a special ENGINE called "dynamic". See the "DYNAMIC ENGINE"
64 with the various compiled-in ENGINEs (see further down for dynamic
133 The new "dynamic" ENGINE provides a low-overhead way to support ENGINE
141 The other use-case for "dynamic" is with applications that wish to
144 them, if you want them, in the form of "dynamic"-loadable
152 How does "dynamic" work?
155 The dynamic ENGINE has a special flag in its implementation such that
156 every time application code asks for the 'dynamic' ENGINE, it in fact
158 multiplexes multiple uses of 'dynamic' in a single application in any
159 way at all) does not get confused by 'dynamic' being used to do many
162 to keep order). The dynamic ENGINE itself provides absolutely no
169     openssl engine -vvvv dynamic
185 (copy of the) 'dynamic' ENGINE will magically morph into the ENGINE
193     ENGINE *e = ENGINE_by_id("dynamic");
203     openssl engine dynamic \
211     openssl engine -vvvv dynamic \
218 such commands through to ENGINEs. As such, you would select "dynamic"
240 How do I build a "dynamic" ENGINE?
248 would have to use "dynamic" to load any such ENGINE - but on the other
252 "dynamic" for hardware support is that any installation using no
258 a shared-library that can be loaded by "dynamic" isn't automated in
270 crypto/engine/ directory as a shared-library for use via the "dynamic"
301         apps/openssl engine -vvvv dynamic \
307 *atalla* ENGINE (ie. *not* the 'dynamic' ENGINE). You can also add