Lines Matching refs:RSA
60 Already there is a problem with the way ENGINE supports RSA, DSA, etc whereby
65 RSA functions (eg. "RSA_free(RSA_new());") will result in large quantities of
72 hooking to ENGINE works from RSA, DSA, DH, RAND, as well as adding new hooking
76 work prior to ENGINE :-). Ie. RSA now has a "RSA_METHOD" pointer again - this
77 was previously replaced by an "ENGINE" pointer and all RSA code that required
79 temporarily get and use the ENGINE's RSA implementation. Apart from being more
80 efficient, switching back to each RSA having an RSA_METHOD pointer also allows
83 have our RSA structure pointing its RSA_METHOD pointer to the software
86 A look at the EVP_CIPHER hooking is most explanatory, the RSA, DSA (etc) cases
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
163 implementations. In other words, the ENGINE_TABLE for RSA will either be empty,
165 represents ENGINEs that implement the single "type" of RSA there is.
185 initialised state. So if RSA code asks for an ENGINE and no ENGINE has
199 mechanism now used by RSA/DSA/..., because there's no such thing as a BIGNUM
205 RSA, DSA, DH, and RAND functions that were fiddled during the original ENGINE