summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/DSA_new.3
diff options
context:
space:
mode:
authorschwarze <>2016-12-10 22:53:31 +0000
committerschwarze <>2016-12-10 22:53:31 +0000
commit9b1c872780bb4e046be1f8e1c302fb9bc042d23d (patch)
treefb9d025763d1cbf4e1f556e7ff5e5e0a654b5bc3 /src/lib/libcrypto/man/DSA_new.3
parentd6345294e36ef19256a039c392d860c2598ea415 (diff)
downloadopenbsd-9b1c872780bb4e046be1f8e1c302fb9bc042d23d.tar.gz
openbsd-9b1c872780bb4e046be1f8e1c302fb9bc042d23d.tar.bz2
openbsd-9b1c872780bb4e046be1f8e1c302fb9bc042d23d.zip
Merge one sentence and the references from dsa(3) to DSA_new(3) and
discard the rest of the text. There is no value in documenting some of the fields of a structure and then going on to say that the structure is intended as opaque. Besides, i doubt that we want such strong marketing of ENGINE support.
Diffstat (limited to 'src/lib/libcrypto/man/DSA_new.3')
-rw-r--r--src/lib/libcrypto/man/DSA_new.326
1 files changed, 22 insertions, 4 deletions
diff --git a/src/lib/libcrypto/man/DSA_new.3 b/src/lib/libcrypto/man/DSA_new.3
index 0bba93b25d..bea1814c8f 100644
--- a/src/lib/libcrypto/man/DSA_new.3
+++ b/src/lib/libcrypto/man/DSA_new.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: DSA_new.3,v 1.3 2016/11/21 13:05:24 schwarze Exp $ 1.\" $OpenBSD: DSA_new.3,v 1.4 2016/12/10 22:53:31 schwarze Exp $
2.\" OpenSSL b97fdb57 Nov 11 09:33:09 2016 +0100 2.\" OpenSSL b97fdb57 Nov 11 09:33:09 2016 +0100
3.\" 3.\"
4.\" This file was written by Ulf Moeller <ulf@openssl.org>. 4.\" This file was written by Ulf Moeller <ulf@openssl.org>.
@@ -48,7 +48,7 @@
48.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 48.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
49.\" OF THE POSSIBILITY OF SUCH DAMAGE. 49.\" OF THE POSSIBILITY OF SUCH DAMAGE.
50.\" 50.\"
51.Dd $Mdocdate: November 21 2016 $ 51.Dd $Mdocdate: December 10 2016 $
52.Dt DSA_NEW 3 52.Dt DSA_NEW 3
53.Os 53.Os
54.Sh NAME 54.Sh NAME
@@ -64,6 +64,8 @@
64.Fa "DSA *dsa" 64.Fa "DSA *dsa"
65.Fc 65.Fc
66.Sh DESCRIPTION 66.Sh DESCRIPTION
67The DSA functions implement the Digital Signature Algorithm.
68.Pp
67.Fn DSA_new 69.Fn DSA_new
68allocates and initializes a 70allocates and initializes a
69.Vt DSA 71.Vt DSA
@@ -90,10 +92,26 @@ and sets an error code that can be obtained by
90.Xr ERR_get_error 3 . 92.Xr ERR_get_error 3 .
91Otherwise it returns a pointer to the newly allocated structure. 93Otherwise it returns a pointer to the newly allocated structure.
92.Sh SEE ALSO 94.Sh SEE ALSO
93.Xr dsa 3 , 95.Xr BN_new 3 ,
96.Xr d2i_DSAPublicKey 3 ,
97.Xr DH_new 3 ,
98.Xr DSA_do_sign 3 ,
99.Xr DSA_dup_DH 3 ,
94.Xr DSA_generate_key 3 , 100.Xr DSA_generate_key 3 ,
95.Xr DSA_generate_parameters 3 , 101.Xr DSA_generate_parameters 3 ,
96.Xr ERR_get_error 3 102.Xr DSA_get_ex_new_index 3 ,
103.Xr DSA_new 3 ,
104.Xr DSA_print 3 ,
105.Xr DSA_set_method 3 ,
106.Xr DSA_SIG_new 3 ,
107.Xr DSA_sign 3 ,
108.Xr DSA_size 3 ,
109.Xr engine 3 ,
110.Xr ERR_get_error 3 ,
111.Xr RSA_new 3
112.Sh STANDARDS
113US Federal Information Processing Standard FIPS 186 (Digital Signature
114Standard, DSS), ANSI X9.30
97.Sh HISTORY 115.Sh HISTORY
98.Fn DSA_new 116.Fn DSA_new
99and 117and