6 gendsa - generate a DSA private key from a set of parameters
27 The B<gendsa> command generates a DSA private key from a DSA parameter file
28 (which will be typically generated by the B<openssl dsaparam> command).
34 =item B<-aes128|-aes192|-aes256|-camellia128|-camellia192|-camellia256|-des|-des3|-idea>
36 These options encrypt the private key with specified
37 cipher before outputting it. A pass phrase is prompted for.
38 If none of these options is specified no encryption is used.
40 =item B<-rand file(s)>
42 a file or files containing random data used to seed the random number
43 generator, or an EGD socket (see L<RAND_egd(3)|RAND_egd(3)>).
44 Multiple files can be specified separated by a OS-dependent character.
45 The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for
50 specifying an engine (by its unique B<id> string) will cause B<gendsa>
51 to attempt to obtain a functional reference to the specified engine,
52 thus initialising it if needed. The engine will then be set as the default
53 for all available algorithms.
57 This option specifies the DSA parameter file to use. The parameters in this
58 file determine the size of the private key. DSA parameters can be generated
59 and examined using the B<openssl dsaparam> command.
65 DSA key generation is little more than random number generation so it is
66 much quicker that RSA key generation for example.
70 L<dsaparam(1)|dsaparam(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,