SSL accelerator support is built in the engine code but you need to actually
use the appropriate library calls in your code to utilize the hardware. The
following code should get you started.
ENGINE *e;
ERR_load_ENGINE_strings; // load engine error strings
e = ENGINE_by_id("cswift"); // use the cryptoswift engine
ENGINE_init(e); // initialize the engine
ENGINE_set_default(e, ENGINE_METHOD_ALL); // tell openssl to use the engine
....
your code here
....
ENGINE_free(e); // cleanup
If the engine fails to load openssl will tell you so. You can also use
"openssl" as the engine id which will use the default software support.
On Tuesday 07 August 2001 02:24 pm, Jared Crane wrote:
> I am looking into the engine version of the software and have a question
> about how it works with hardware accelerators. My concern is how will
> ssl behave if I build for an accelerator and for some reason there isn't
> one, it breaks or it is no longer available?
>
> Please send any replies to me as I have not subscribed to the list.
>
> Thanks,
> Jared
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
