Lines Matching +full:zero +full:- +full:initialised
43 - ENGINE cryptographic module support
175 reference-counted mechanism to allow them to be dynamically loaded in and
181 RSA_METHOD - for providing alternative RSA implementations
183 - similarly for other OpenSSL APIs
184 EVP_CIPHER - potentially multiple cipher algorithms (indexed by 'nid')
185 EVP_DIGEST - potentially multiple hash algorithms (indexed by 'nid')
186 key-loading - loading public and/or private EVP_PKEY keys
191 treated as handles - i.e. not only as pointers, but also as references to
196 ENGINE objects have two levels of reference-counting to match the way in
198 inherently a B<structural> reference - a structural reference is required
203 initialised and able to use any of its cryptographic
209 implicitly contains a structural reference as well - however to avoid
210 difficult-to-find programming bugs, it is recommended to treat the two
212 ENGINE, you have a guarantee that the ENGINE has been initialised and
213 is ready to perform cryptographic operations, and will remain initialised
219 iterating across OpenSSL's internal linked-list of loaded
228 released by a corresponding to call to the ENGINE_free() function - the
234 structural reference will internally obtain another reference - typically
237 OpenSSL's internal list is ENGINE_add() - if this function returns success,
244 ENGINE list - they will return a new structural reference to the next (or
262 call the ENGINE_init() function. This returns zero if the ENGINE was not
263 already operational and couldn't be successfully initialised (e.g. lack of
275 algorithm-specific types in OpenSSL, such as RSA, DSA, EVP_CIPHER_CTX, etc.
292 functional reference to an initialised ENGINE whose implementation should be
294 will operate with a NULL ENGINE handle - this usually equates to using the
309 instead the only way for the state table to return a non-NULL ENGINE to the
314 indexed by 'nid', these flags and cached-responses are distinct for each 'nid'
324 "visible" ENGINEs from which it has to operate - at start-up, this list is
329 made visible to OpenSSL - this is controlled by calling the various "load"
333 the program and loaded into memory at run-time) does not mean they are
334 "registered" or called into use by OpenSSL automatically - that behaviour
338 OpenSSL automatically use at run-time any ENGINE that is able to
339 successfully initialise - i.e. to assume that this corresponds to
344 source code to openssl's built-in utilities as guides.
357 OpenSSL should use its built-in software as per usual. The following code
385 I<Automatically using built-in ENGINE implementations>
389 OpenSSL - if there is an ENGINE that implements it and can be initialised,
407 OpenSSL. This mechanism is entirely based on the use of name-value pairs
424 so that it can be initialised for use. This could include the path to any
426 smart-card identifiers, passwords to initialise protected devices,
433 this in the descriptions attached to built-in control commands and/or in
439 name of the ENGINE it wishes to use, a table of string-pairs for use before
441 the string-pairs used for control commands consist of a command "name"
442 followed by the command "parameter" - the parameter could be NULL in some
454 while (pre_num--) {
456 fprintf(stderr, "Failed command (%s - %s:%s)\n", engine_id,
473 while (post_num--) {
475 fprintf(stderr, "Failed command (%s - %s:%s)\n", engine_id,
488 relax the semantics of the function - if set nonzero it will only return
497 It is possible to discover at run-time the names, numerical-ids, descriptions
532 ENGINE_HAS_CTRL_FUNCTION returns FALSE (zero),
551 description. ENGINE_CTRL_GET_FLAGS returns a bitwise-OR'd mask of the following
560 informational to the caller - this flag will prevent the command being usable
561 for any higher-level ENGINE functions such as ENGINE_ctrl_cmd_string().
562 "INTERNAL" commands are not intended to be exposed to text-based configuration
568 might query various ENGINEs to see if they implement "FOO_GET_VENDOR_LOGO_GIF" -
569 and ENGINE could therefore decide whether or not to support this "foo"-specific
579 Ignored in set-user-ID and set-group-ID programs.
669 Copyright 2002-2024 The OpenSSL Project Authors. All Rights Reserved.