summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/dsa.3
diff options
context:
space:
mode:
authorschwarze <>2016-12-10 22:53:31 +0000
committerschwarze <>2016-12-10 22:53:31 +0000
commita88f3c227f55731a4a000617a2b4735f0f0aaf86 (patch)
treefb9d025763d1cbf4e1f556e7ff5e5e0a654b5bc3 /src/lib/libcrypto/man/dsa.3
parent658ebcf70d6682438d1d7788358e0e857753530a (diff)
downloadopenbsd-a88f3c227f55731a4a000617a2b4735f0f0aaf86.tar.gz
openbsd-a88f3c227f55731a4a000617a2b4735f0f0aaf86.tar.bz2
openbsd-a88f3c227f55731a4a000617a2b4735f0f0aaf86.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.3')
-rw-r--r--src/lib/libcrypto/man/dsa.374
1 files changed, 0 insertions, 74 deletions
diff --git a/src/lib/libcrypto/man/dsa.3 b/src/lib/libcrypto/man/dsa.3
deleted file mode 100644
index 78493635fb..0000000000
--- a/src/lib/libcrypto/man/dsa.3
+++ /dev/null
@@ -1,74 +0,0 @@
1.\" $OpenBSD: dsa.3,v 1.5 2016/12/10 22:22:59 schwarze Exp $
2.\"
3.Dd $Mdocdate: December 10 2016 $
4.Dt DSA 3
5.Os
6.Sh NAME
7.Nm dsa
8.Nd Digital Signature Algorithm
9.Sh SYNOPSIS
10.In openssl/dsa.h
11.Sh DESCRIPTION
12These functions implement the Digital Signature Algorithm (DSA).
13The generation of shared DSA parameters is described in
14.Xr DSA_generate_parameters 3 ;
15.Xr DSA_generate_key 3
16describes how to generate a signature key.
17Signature generation and verification are described in
18.Xr DSA_sign 3 .
19.Pp
20The
21.Vt DSA
22structure consists of several BIGNUM components.
23.Bd -literal
24typedef struct {
25 BIGNUM *p; // prime number (public)
26 BIGNUM *q; // 160-bit subprime, q | p-1 (public)
27 BIGNUM *g; // generator of subgroup (public)
28 BIGNUM *priv_key; // private key x
29 BIGNUM *pub_key; // public key y = g^x
30 // ...
31} DSA;
32.Ed
33.Pp
34In public keys,
35.Fa priv_key
36is
37.Dv NULL .
38.Pp
39Note that DSA keys may use non-standard
40.Vt DSA_METHOD
41implementations, either directly or by the use of
42.Vt ENGINE
43modules.
44In some cases (e.g. an
45.Vt ENGINE
46providing support for hardware-embedded keys), these
47.Vt BIGNUM
48values will not be used by the implementation or may be used for
49alternative data storage.
50For this reason, applications should generally avoid using
51.Vt DSA
52structure elements directly and instead use API functions to query
53or modify keys.
54.Sh SEE ALSO
55.Xr BN_new 3 ,
56.Xr d2i_DSAPublicKey 3 ,
57.Xr DH_new 3 ,
58.Xr DSA_do_sign 3 ,
59.Xr DSA_dup_DH 3 ,
60.Xr DSA_generate_key 3 ,
61.Xr DSA_generate_parameters 3 ,
62.Xr DSA_get_ex_new_index 3 ,
63.Xr DSA_new 3 ,
64.Xr DSA_print 3 ,
65.Xr DSA_set_method 3 ,
66.Xr DSA_SIG_new 3 ,
67.Xr DSA_sign 3 ,
68.Xr DSA_size 3 ,
69.Xr engine 3 ,
70.Xr ERR 3 ,
71.Xr rsa 3
72.Sh STANDARDS
73US Federal Information Processing Standard FIPS 186 (Digital Signature
74Standard, DSS), ANSI X9.30