X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=README.ENGINE;h=0d698b7446bccb1b36f9d5333eb07fcc39ad2440;hp=b30206c0edbb85c2cc1190194d365e3c7e73b57e;hb=a77e023ab409ef0be7d6c232b9685652d62f0763;hpb=b22bda21a15b46094db379ffba55e3481e60223f

diff --git a/README.ENGINE b/README.ENGINE
index b30206c0ed..0d698b7446 100644
--- a/README.ENGINE
+++ b/README.ENGINE
@@ -13,11 +13,10 @@
       o CryptoSwift
       o Compaq Atalla
       o nCipher CHIL
+      o Nuron
 
   A number of things are still needed and are being worked on:
 
-      o An openssl utility command to handle or at least check available
-        engines.
       o A better way of handling the methods that are handled by the
         engines.
       o Documentation!
@@ -25,25 +24,6 @@
   What already exists is fairly stable as far as it has been tested, but
   the test base has been a bit small most of the time.
 
-  Because of this experimental status and what's lacking, the ENGINE
-  component is not yet part of the default OpenSSL distribution.  However,
-  we have made a separate kit for those who want to try this out, to be
-  found in the same places as the default OpenSSL distribution, but with
-  "-engine-" being part of the kit file name.  For example, version 0.9.6
-  is distributed in the following two files:
-
-      openssl-0.9.6.tar.gz
-      openssl-engine-0.9.6.tar.gz
-
-  NOTES
-  =====
-
-  openssl-engine-0.9.6.tar.gz does not depend on openssl-0.9.6.tar, you do
-  not need to download both.
-
-  openssl-engine-0.9.6.tar.gz is usable even if you don't have an external
-  crypto device.  The internal OpenSSL functions are contained in the
-  engine "openssl", and will be used by default.
 
   No external crypto device is chosen unless you say so.  You have actively
   tell the openssl utility commands to use it through a new command line
@@ -52,3 +32,12 @@
   device, or the built-in crypto routines will be used, just as in the
   default OpenSSL distribution.
 
+
+  PROBLEMS
+  ========
+
+  It seems like the ENGINE part doesn't work too well with Cryptoswift on
+  Win32.  A quick test done right before the release showed that trying
+  "openssl speed -engine cswift" generated errors.  If the DSO gets enabled,
+  an attempt is made to write at memory address 0x00000002.
+