summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorMarkus Friedl <markus@cvs.openbsd.org>2003-05-11 21:36:19 +0000
committerMarkus Friedl <markus@cvs.openbsd.org>2003-05-11 21:36:19 +0000
commit681786ca0f0296c98a2f875f9c94951faeb4a1f6 (patch)
treeba272d0725fc0b86efe274a962c1ccda3a98b8f3 /lib
parent3d6ad47a2d10491393e8ac81552dcb696a228aec (diff)
import 0.9.7b (without idea and rc5)
Diffstat (limited to 'lib')
-rw-r--r--lib/libssl/src/doc/HOWTO/keys.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/libssl/src/doc/HOWTO/keys.txt b/lib/libssl/src/doc/HOWTO/keys.txt
index 7ae2a3a1183..45f42eaaf1b 100644
--- a/lib/libssl/src/doc/HOWTO/keys.txt
+++ b/lib/libssl/src/doc/HOWTO/keys.txt
@@ -40,9 +40,9 @@ consider insecure or to be insecure pretty soon.
3. To generate a DSA key
-A DSA key can be used for signing only. This is important to keep
-in mind to know what kind of purposes a certificate request with a
-DSA key can really be used for.
+A DSA key can be used both for signing only. This is important to
+keep in mind to know what kind of purposes a certificate request with
+a DSA key can really be used for.
Generating a key for the DSA algorithm is a two-step process. First,
you have to generate parameters from which to generate the key: