5 With OpenSSL 0.9.6, a new component has been added to support external
6 crypto devices, for example accelerator cards. The component is called
7 ENGINE, and has still a pretty experimental status and almost no
8 documentation. It's designed to be faily easily extensible by the
11 There's currently built-in support for the following crypto devices:
17 A number of things are still needed and are being worked on:
19 o An openssl utility command to handle or at least check available
21 o A better way of handling the methods that are handled by the
25 What already exists is fairly stable as far as it has been tested, but
26 the test base has been a bit small most of the time.
29 No external crypto device is chosen unless you say so. You have actively
30 tell the openssl utility commands to use it through a new command line
31 switch called "-engine". And if you want to use the ENGINE library to
32 do something similar, you must also explicitely choose an external crypto
33 device, or the built-in crypto routines will be used, just as in the
34 default OpenSSL distribution.
40 It seems like the ENGINE part doesn't work too well with Cryptoswift on
41 Win32. A quick test done right before the release showed that trying
42 "openssl speed -engine cswift" generated errors. If the DSO gets enabled,
43 an attempt is made to write at memory address 0x00000002.