Lines Matching refs:commands

406 "commands" and expose them to OpenSSL and any applications based on
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
427 logging information, etc etc. This class of commands typically needs to be
429 calling ENGINE_init(). The other class of commands consist of settings or
431 place, and these commands may work either before or after ENGINE_init(), or
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"
444 (issuing the "pre" commands beforehand and the "post" commands afterwards)
492 only supplying commands specific to the given ENGINE so we set this to
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
503 commands implemented by ENGINEs should be numbered from. Any command value
507 It is using these "core" control commands that one can discover the control
508 commands implemented by a given ENGINE, specifically the commands:
520 Whilst these commands are automatically processed by the OpenSSL framework code,
526 simply pass all these "core" control commands directly to the ENGINE's ctrl()
528 reply to these "discovery" commands itself. If that flag is not set, then the
533      all other commands fail.
534  if a ctrl() handler was supplied but no array of control commands;
536      all other commands fail.
537  if a ctrl() handler and array of control commands was supplied;
539      all other commands proceed processing ...
541 If the ENGINE's array of control commands is empty then all other commands will
547 command name exists, and the remaining commands take a command identifier and
548 return properties of the corresponding commands. All except
562 "INTERNAL" commands are not intended to be exposed to text-based configuration
565 commands data of any arbitrary type. These commands are supported in the
567 supports certain specific commands it might want to use (e.g. application "foo"