Lines Matching refs:code
7 the "ENGINE" code. So it serves a double purpose of being a "ENGINE internals
66 ENGINE code being linked in *and* because of that DSA, DH, and RAND also. If we
77 was previously replaced by an "ENGINE" pointer and all RSA code that required
93 cipher-specific ENGINE code is asked for an ENGINE pointer (a functional
96 ENGINE code will return NULL because no ENGINEs will have had any cipher
118 The "cipher-specific ENGINE code" I mentioned is implemented in tb_cipher.c but
119 in essence it is simply an instantiation of "ENGINE_TABLE" code for use by
120 EVP_CIPHER code. tb_digest.c is virtually identical but, of course, it is for
121 use by EVP_MD code. Ditto for tb_rsa.c, tb_dsa.c, etc. These instantiations of
124 EVP_CIPHER code will link at most code relating to EVP_CIPHER, tb_cipher.c, core
125 ENGINE code that is independent of class, and of course the ENGINE
127 class-specific ENGINE code for digests, RSA, etc nor will it bleed over into
128 other APIs, such as the RSA/DSA/etc library code.
158 RSA, DSA, DH, and RAND all have their own ENGINE_TABLE code as well, and the
169 application or EVP_CIPHER code releases its last reference to an ENGINE, the
170 ENGINE_PILE code may still have references and thus those ENGINEs will stay
175 code despite the fact the application may use only ciphers, for example). This
181 functions. These functions are internal-only and each part of ENGINE code that
183 callback with the "engine_cleanup" code. The other part of this that makes it
185 initialised state. So if RSA code asks for an ENGINE and no ENGINE has
186 registered an implementation, the code will simply return NULL and the tb_rsa.c
195 code to have to register a cleanup.
201 application code to automatically hook and use ENGINE supplied bignum functions
