5 dhparam - DH parameter manipulation and generation
26 This command is used to manipulate DH parameter files.
32 =item B<-inform DER|PEM>
34 This specifies the input format. The B<DER> option uses an ASN1 DER encoded
35 form compatible with the PKCS#3 DHparameter structure. The PEM form is the
36 default format: it consists of the B<DER> format base64 encoded with
37 additional header and footer lines.
39 =item B<-outform DER|PEM>
41 This specifies the output format, the options have the same meaning as the
44 =item B<-in> I<filename>
46 This specifies the input filename to read parameters from or standard input if
47 this option is not specified.
49 =item B<-out> I<filename>
51 This specifies the output filename parameters to. Standard output is used
52 if this option is not present. The output filename should B<not> be the same
53 as the input filename.
57 If this option is used, DSA rather than DH parameters are read or created;
58 they are converted to DH format. Otherwise, "strong" primes (such
59 that (p-1)/2 is also prime) will be used for DH parameter generation.
61 DH parameter generation with the B<-dsaparam> option is much faster,
62 and the recommended exponent length is shorter, which makes DH key
63 exchange more efficient. Beware that with such DSA-style DH
64 parameters, a fresh DH key should be created for each use to
65 avoid small-subgroup attacks that may be possible otherwise.
69 The generator to use, either 2 or 5. 2 is the default. If present then the
70 input file is ignored and parameters are generated instead.
72 =item B<-rand> I<file(s)>
74 a file or files containing random data used to seed the random number
75 generator, or an EGD socket (see L<RAND_egd(3)|RAND_egd(3)>).
76 Multiple files can be specified separated by a OS-dependent character.
77 The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for
82 this option specifies that a parameter set should be generated of size
83 I<numbits>. It must be the last option. If not present then a value of 512
84 is used. If this option is present then the input file is ignored and
85 parameters are generated instead.
89 this option inhibits the output of the encoded version of the parameters.
93 this option prints out the DH parameters in human readable form.
97 this option converts the parameters into C code. The parameters can then
98 be loaded by calling the B<get_dh>I<numbits>B<()> function.
102 specifying an engine (by it's unique B<id> string) will cause B<req>
103 to attempt to obtain a functional reference to the specified engine,
104 thus initialising it if needed. The engine will then be set as the default
105 for all available algorithms.
111 The program B<dhparam> combines the functionality of the programs B<dh> and
112 B<gendh> in previous versions of OpenSSL and SSLeay. The B<dh> and B<gendh>
113 programs are retained for now but may have different purposes in future
118 PEM format DH parameters use the header and footer lines:
120 -----BEGIN DH PARAMETERS-----
121 -----END DH PARAMETERS-----
123 OpenSSL currently only supports the older PKCS#3 DH, not the newer X9.42
126 This program manipulates DH parameters not keys.
130 There should be a way to generate and manipulate DH keys.
134 L<dsaparam(1)|dsaparam(1)>
138 The B<dhparam> command was added in OpenSSL 0.9.5.
139 The B<-dsaparam> option was added in OpenSSL 0.9.6.