Home | History | Annotate | Download | only in engine

Lines Matching full:commands

131  * control commands on their own. Without this flag, ENGINE_ctrl() handles these
132 * control commands on behalf of the ENGINE using their "cmd_defns" data. */
137 * commands are called in sequence as part of some stateful process like
174 /* NB: These 3 control commands are deprecated and should not be used. ENGINEs
175 * relying on these commands should compile conditional support for
178 * "discovered" by calling applications. The fact these control commands
203 /* These control commands allow an application to deal with an arbitrary engine
205 * COMMANDS because zero is used to indicate 'end-of-list'. Other commands,
213 * handler need only implement its own commands - the above "meta" commands will
217 * all the remaining control commands will return failure, so it is worth
222 * engine. Returns zero if no ctrl commands are supported. */
247 * commands from this value. (ie. ENGINE_CMD_BASE, ENGINE_CMD_BASE + 1, etc). */
250 /* NB: These 2 nCipher "chil" control commands are deprecated, and their
251 * functionality is now available through ENGINE-specific control commands
253 * commands should be migrated to the more general command handling before these
266 /* If an ENGINE supports its own specific control commands and wishes the
267 * framework to handle the above 'ENGINE_CMD_***'-manipulation commands on its
270 * supports the stated commands (ie. the "cmd_num" entries as described by the
422 /* Send parametrised control commands to the engine. The possibilities to send
426 * reference to an engine, but many control commands may require the engine be
427 * functional. The caller should be aware of trying commands that require an
438 * command name instead of a command number, and can handle optional commands.