summaryrefslogtreecommitdiff
path: root/doc/HOWTO/keys.txt
diff options
context:
space:
mode:
authorsangwan.kwon <sangwan.kwon@samsung.com>2015-12-18 14:13:27 +0900
committersangwan.kwon <sangwan.kwon@samsung.com>2015-12-18 14:14:57 +0900
commit6a424b1e0ec46f307697ffe971a3e46b3129f693 (patch)
tree063e9bd46b09b57192b9af486e0649a139c40712 /doc/HOWTO/keys.txt
parent7bb2e75e597abc44122a538b5935153bf1ecb9ec (diff)
parent2b3ef38d58c1bb0abff4bf611177fc76e78325fa (diff)
downloadopenssl-tizen.tar.gz
openssl-tizen.tar.bz2
openssl-tizen.zip
Upgrade Upstream version 1.0.2eHEADsubmit/tizen/20151228.015607tizen
Change-Id: If6afd73ecd5ef4548b9389eca6e53946aac3b9f2
Diffstat (limited to 'doc/HOWTO/keys.txt')
-rw-r--r--doc/HOWTO/keys.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/HOWTO/keys.txt b/doc/HOWTO/keys.txt
index 7ae2a3a..ba0314f 100644
--- a/doc/HOWTO/keys.txt
+++ b/doc/HOWTO/keys.txt
@@ -40,9 +40,8 @@ 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 for signing only. It is important to
+know what 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: