Lines Matching full:engines

330 Due to the modular nature of the \s-1ENGINE API,\s0 pointers to ENGINEs need to be
344 implementations. Indeed it's quite possible that most ENGINEs will not
345 initialise at all in typical environments, as ENGINEs are typically used to
358 This basic type of reference is used for instantiating new ENGINEs,
360 ENGINEs, reading information about an \s-1ENGINE,\s0 etc. Essentially a structural
422 algorithms and modes, and ENGINEs can support arbitrarily many of them.
438 this question it must iterate across all the registered ENGINEs in the
461 \&\*(L"visible\*(R" ENGINEs from which it has to operate \- at start-up, this list is
469 The fact that ENGINEs are made visible to OpenSSL (and thus are linked into
485 if any ENGINEs are loaded, even if not registered or used, it was necessary to
532 \& /* Load all bundled ENGINEs into memory and make them visible */
539 \&\s-1RSA\s0 key, any bundled ENGINEs that implement \s-1RSA_METHOD\s0 will be passed to
550 arbitrary configuration \*(L"directives\*(R" directly to such ENGINEs. It is also
557 supported control commands and simply prefer to pass settings into ENGINEs
645 commands implemented by ENGINEs should be numbered from. Any command value
716 might query various ENGINEs to see if they implement \*(L"\s-1FOO_GET_VENDOR_LOGO_GIF\*(R"\s0 \-
723 The path to the engines directory.