[openssl-commits] [openssl] master update

[Dr. Stephen Henson]

The branch master has been updated
       via  0c787647ded59a81311d905024bc93df5d3a061c (commit)
      from  167548061dd00cc1f2ea36b6c3113165f1b643a4 (commit)


- Log -----------------------------------------------------------------
commit 0c787647ded59a81311d905024bc93df5d3a061c
Author: Dr. Stephen Henson <steve at openssl.org>
Date:   Thu Jan 28 23:57:46 2016 +0000

    update DSA docs
    
    Reviewed-by: Andy Polyakov <appro at openssl.org>

-----------------------------------------------------------------------

Summary of changes:
 doc/crypto/d2i_DSAPublicKey.pod | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/doc/crypto/d2i_DSAPublicKey.pod b/doc/crypto/d2i_DSAPublicKey.pod
index 549fab0..7acb329 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