diff options
author | Dr. Stephen Henson <steve@openssl.org> | 2016-01-28 23:57:46 +0000 |
---|---|---|
committer | Dr. Stephen Henson <steve@openssl.org> | 2016-02-01 15:12:54 +0000 |
commit | 0c787647ded59a81311d905024bc93df5d3a061c (patch) | |
tree | b21300eacd4be4543bd11d119f42d09d0af0d2a2 | |
parent | 167548061dd00cc1f2ea36b6c3113165f1b643a4 (diff) |
update DSA docs
Reviewed-by: Andy Polyakov <appro@openssl.org>
-rw-r--r-- | doc/crypto/d2i_DSAPublicKey.pod | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/doc/crypto/d2i_DSAPublicKey.pod b/doc/crypto/d2i_DSAPublicKey.pod index 549fab0f8e..7acb329f23 100644 --- a/doc/crypto/d2i_DSAPublicKey.pod +++ b/doc/crypto/d2i_DSAPublicKey.pod @@ -62,11 +62,9 @@ offers no private key security. The B<DSA_PUBKEY> functions should be used in preference to the B<DSAPublicKey> functions when encoding public keys because they use a standard format. -The B<DSAPublicKey> functions use an non standard format the actual data encoded -depends on the value of the B<write_params> field of the B<a> key parameter. -If B<write_params> is zero then only the B<pub_key> field is encoded as an -B<INTEGER>. If B<write_params> is 1 then a B<SEQUENCE> consisting of the -B<p>, B<q>, B<g> and B<pub_key> respectively fields are encoded. +The B<DSAPublicKey> functions use a non standard format which is a +B<SEQUENCE> consisting of the B<p>, B<q>, B<g> and B<pub_key> fields +respectively. The B<DSAPrivateKey> functions also use a non standard structure consisting consisting of a SEQUENCE containing the B<p>, B<q>, B<g> and B<pub_key> and |