X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=README.ENGINE;h=230dc82a87ba72b8c5ce0bbebf87f2ecdf669c2a;hp=643d0cb51f7352a126313f0873c936b41f66e792;hb=14f61f81f22db55f0ea79105a493398c1c2e04b7;hpb=3b80e3aa9e0c4543dbd8f7ef1794a1db0a2ec271 diff --git a/README.ENGINE b/README.ENGINE index 643d0cb51f..230dc82a87 100644 --- a/README.ENGINE +++ b/README.ENGINE @@ -13,11 +13,9 @@ There are currently built-in ENGINE implementations for the following crypto devices: - o CryptoSwift - o Compaq Atalla + o Microsoft CryptoAPI + o VIA Padlock o nCipher CHIL - o Nuron - o Broadcom uBSec In addition, dynamic binding to external ENGINE implementations is now provided by a special ENGINE called "dynamic". See the "DYNAMIC ENGINE" @@ -154,7 +152,7 @@ shared-library that contains the ENGINE implementation, and "NO_VCHECK" might possibly be useful if there is a minor version conflict and you (or a vendor helpdesk) is convinced you can safely ignore it. - "ENGINE_ID" is probably only needed if a shared-library implements + "ID" is probably only needed if a shared-library implements multiple ENGINEs, but if you know the engine id you expect to be using, it doesn't hurt to specify it (and this provides a sanity check if nothing else). "LIST_ADD" is only required if you actually wish the @@ -174,7 +172,7 @@ ENGINE *e = ENGINE_by_id("dynamic"); ENGINE_ctrl_cmd_string(e, "SO_PATH", "/lib/libfoo.so", 0); - ENGINE_ctrl_cmd_string(e, "ENGINE_ID", "foo", 0); + ENGINE_ctrl_cmd_string(e, "ID", "foo", 0); ENGINE_ctrl_cmd_string(e, "LOAD", NULL, 0); ENGINE_ctrl_cmd_string(e, "CMD_FOO", "some input data", 0); @@ -184,7 +182,7 @@ openssl engine dynamic \ -pre SO_PATH:/lib/libfoo.so \ - -pre ENGINE_ID:foo \ + -pre ID:foo \ -pre LOAD \ -pre "CMD_FOO:some input data" @@ -192,7 +190,7 @@ openssl engine -vvvv dynamic \ -pre SO_PATH:/lib/libfoo.so \ - -pre ENGINE_ID:foo \ + -pre ID:foo \ -pre LOAD Applications that support the ENGINE API and more specifically, the