aboutsummaryrefslogtreecommitdiffstats
path: root/lib/crypto
diff options
context:
space:
mode:
authorHans Nilsson <[email protected]>2017-11-21 14:33:54 +0100
committerHans Nilsson <[email protected]>2017-11-21 14:33:54 +0100
commite0f51124fb37cc6287bc710a537b92d3a179cc72 (patch)
treef7c20ba9d2d67b0e23109cb752b056fa25b43ce9 /lib/crypto
parent223b6a3f4d53f7d5b5d0b9756c1eec4a5b8c862b (diff)
downloadotp-e0f51124fb37cc6287bc710a537b92d3a179cc72.tar.gz
otp-e0f51124fb37cc6287bc710a537b92d3a179cc72.tar.bz2
otp-e0f51124fb37cc6287bc710a537b92d3a179cc72.zip
crypto: Changes after review
Diffstat (limited to 'lib/crypto')
-rw-r--r--lib/crypto/doc/src/engine_keys.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/lib/crypto/doc/src/engine_keys.xml b/lib/crypto/doc/src/engine_keys.xml
index 64d1e6c2a3..38714fed8a 100644
--- a/lib/crypto/doc/src/engine_keys.xml
+++ b/lib/crypto/doc/src/engine_keys.xml
@@ -39,8 +39,8 @@
for details and how to load an Engine.
</p>
<p>
- In addition to provide alternative cryptographic implementations, an engine could provide a storage for
- private or public keys. Such a storage could be made safer than the normal file system. Such techniques are not
+ An engine could among other tasks provide a storage for
+ private or public keys. Such a storage could be made safer than the normal file system. Thoose techniques are not
described in this User's Guide. Here we concentrate on how to use private or public keys stored in
such an engine.
</p>
@@ -50,7 +50,8 @@
</p>
<p>
OTP/Crypto requires that the user provides two or three items of information about the key. The application used
- by the user is usually on a higher level, for example <seealso marker="ssl:ssl_app#application">SSL</seealso>. If using
+ by the user is usually on a higher level, for example in
+ <seealso marker="ssl:ssl#key_option_def">SSL</seealso>. If using
the crypto application directly, it is required that:
</p>
<list>