Lines Matching full:these

42  * These flags are used to control combinations of algorithm (methods) by
73  * these control commands on behalf of the ENGINE using their "cmd_defns"
99  * ENGINEs can support their own command types, and these flags are used in
130  * NB: These 3 control commands are deprecated and should not be used.
131  * ENGINEs relying on these commands should compile conditional support for
132  * compatibility (eg. if these symbols are defined) but should also migrate
134  * can be "discovered" by calling applications. The fact these control
141  * These flags are used to tell the ctrl function what should be done. All
165  * These control commands allow an application to deal with an arbitrary
167  * THESE COMMANDS because zero is used to indicate 'end-of-list'. Other
169  * error. An ENGINE can choose to implement these ctrl functions, and can
227  * NB: These 2 nCipher "chil" control commands are deprecated, and their
229  * (exposed through the above-mentioned 'CMD'-handling). Code using these 2
231  * these are removed.
282  * These callback types are for an ENGINE's handler for cipher and digest logic.
283  * These handlers have these prototypes;
286  * Looking at how to implement these handlers in the case of cipher support, if
305  * STRUCTURE functions ... all of these functions deal with pointers to
408  * These functions register all support from the above categories. Note, use
409  * of these functions can result in static linkage of code your application
484  * These functions are useful for manufacturing new ENGINE structures. They
488  * These are also here so that the ENGINE structure doesn't have to be
529 /* These functions allow control over any per-structure ENGINE data. */
546  * These return values from within the ENGINE structure. These can be useful
602  * FUNCTIONAL functions. These functions deal with ENGINE structures that
605  * creating new engine types, and other "list" operations. These functions
606  * actually deal with ENGINEs that are to be used. As such these functions
667  * These functions can be used to get a functional reference to perform
729  * by the "dynamic" ENGINE, these types are needed. The 'dynamic_fns'
732  * library. These should be used/set in the loaded library code so that the
736  * these callbacks need to be set or not.
748  * use these types so we (and any other dependent code) can simplify a bit??