summaryrefslogtreecommitdiff
path: root/README.ENGINE
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2000-09-24 14:48:51 +0000
committerRichard Levitte <levitte@openssl.org>2000-09-24 14:48:51 +0000
commit56245be46d7e18f17e263e46205e73d00bd8d16b (patch)
treeeb58a9fb1eecdb42e6a852331bb3c14bc6894d6c /README.ENGINE
parenteb206eb8be7d177ede493a40c50e620489fbd5e9 (diff)
downloadopenssl-new-56245be46d7e18f17e263e46205e73d00bd8d16b.tar.gz
Change the Windows building scripts to enable DSO_WIN32.
Diffstat (limited to 'README.ENGINE')
-rw-r--r--README.ENGINE9
1 files changed, 9 insertions, 0 deletions
diff --git a/README.ENGINE b/README.ENGINE
index b30206c0ed..3d88ed152f 100644
--- a/README.ENGINE
+++ b/README.ENGINE
@@ -52,3 +52,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.
+