Lines Matching full:commands

546 \&\*(L"commands\*(R" and expose them to OpenSSL and any applications based on
553 available \*(L"control commands\*(R", providing a more flexible configuration
557 supported control commands and simply prefer to pass settings into ENGINEs
560 Before illustrating how control commands work, it is worth mentioning what
562 control commands; the first is to provide the necessary details to the
567 logging information, etc etc. This class of commands typically needs to be
569 calling \fBENGINE_init()\fR. The other class of commands consist of settings or
571 place, and these commands may work either before or after \fBENGINE_init()\fR, or
573 this in the descriptions attached to built-in control commands and/or in
576 \&\fIIssuing control commands to an \s-1ENGINE\s0\fR
581 the string-pairs used for control commands consist of a command \*(L"name\*(R"
584 (issuing the \*(L"pre\*(R" commands beforehand and the \*(L"post\*(R" commands afterwards)
634 only supplying commands specific to the given \s-1ENGINE\s0 so we set this to
637 \&\fIDiscovering supported control commands\fR
640 and input parameters of the control commands supported by an \s-1ENGINE\s0 using a
641 structural reference. Note that some control commands are defined by OpenSSL
642 itself and it will intercept and handle these control commands on behalf of the
645 commands implemented by ENGINEs should be numbered from. Any command value
649 It is using these \*(L"core\*(R" control commands that one can discover the control
650 commands implemented by a given \s-1ENGINE,\s0 specifically the commands:
664 Whilst these commands are automatically processed by the OpenSSL framework code,
670 simply pass all these \*(L"core\*(R" control commands directly to the \s-1ENGINE\s0's \fBctrl()\fR
672 reply to these \*(L"discovery\*(R" commands itself. If that flag is not set, then the
678 \&     all other commands fail.
679 \& if a ctrl() handler was supplied but no array of control commands;
681 \&     all other commands fail.
682 \& if a ctrl() handler and array of control commands was supplied;
684 \&     all other commands proceed processing ...
687 If the \s-1ENGINE\s0's array of control commands is empty then all other commands will
693 command name exists, and the remaining commands take a command identifier and
694 return properties of the corresponding commands. All except
710 \&\*(L"\s-1INTERNAL\*(R"\s0 commands are not intended to be exposed to text-based configuration
713 commands data of any arbitrary type. These commands are supported in the
715 supports certain specific commands it might want to use (e.g. application \*(L"foo\*(R"