Lines Matching refs:control
280 of state to control which implementations are available for a given
335 is something for the application to control. Some applications
413 available "control commands", providing a more flexible configuration
417 supported control commands and simply prefer to pass settings into ENGINEs
420 Before illustrating how control commands work, it is worth mentioning what
422 control commands; the first is to provide the necessary details to the
433 this in the descriptions attached to built-in control commands and/or in
436 I<Issuing control commands to an ENGINE>
441 the string-pairs used for control commands consist of a command "name"
495 I<Discovering supported control commands>
498 and input parameters of the control commands supported by an ENGINE using a
499 structural reference. Note that some control commands are defined by OpenSSL
500 itself and it will intercept and handle these control commands on behalf of the
501 ENGINE, i.e. the ENGINE's ctrl() handler is not used for the control command.
502 F<< <openssl/engine.h> >> defines an index, ENGINE_CMD_BASE, that all control
507 It is using these "core" control commands that one can discover the control
524 the ENGINE's flags, and it can expose an array of control command descriptions.
526 simply pass all these "core" control commands directly to the ENGINE's ctrl()
534 if a ctrl() handler was supplied but no array of control commands;
537 if a ctrl() handler and array of control commands was supplied;
541 If the ENGINE's array of control commands is empty then all other commands will
564 operations via ENGINE_ctrl(), including passing to and/or from the control
603 global table flags which are used to control the registration behaviour of
646 used to control various behaviours of an ENGINE.
