On Sun, Nov 25, 2001 at 12:16:44PM -0500, NN Poster wrote: > Summary > ======= > Command line option "-name" and configuration file option "default_ca" for > ca(1) not explained in POD. > > > Description > =========== > POD file for ca(1) lists a command line option "-name" in the synopsis > section but the option is not further explained. Similarly, the sample > OpenSSL configuration file uses option "default_ca", which is not explained > in ca(1) POD either.
True. Actually the behaviour of ca(1) w/r/t configuration file sections appears to be too weird to document: certain options are not looked for in the section given by '-name' or 'default_ca', but directly in the 'ca' section. I've changed the documentation as follows for now: Index: ca.pod =================================================================== RCS file: /e/openssl/cvs/openssl/doc/apps/ca.pod,v retrieving revision 1.12 diff -u -u -r1.12 ca.pod --- ca.pod 2001/10/25 08:25:19 1.12 +++ ca.pod 2001/11/26 12:12:06 @@ -57,6 +57,11 @@ specifies the configuration file to use. +=item B<-name section> + +specifies the configuration file section to use (overrides +B<default_ca> in the B<ca> section). + =item B<-in filename> an input filename containing a single certificate request to be @@ -225,9 +230,21 @@ =back =head1 CONFIGURATION FILE OPTIONS + +The section of the configuration file containing options for B<ca> +is found as follows: If the B<-name> command line option is used, +then it names the section to be used. Otherwise the section to +be used must be named in the B<default_ca> option of the B<ca> section +of the configuration file (or in the default section of the +configuration file). Besides B<default_ca>, the following options are +read directly from the B<ca> section: + RANDFILE + preserve + msie_hack +With the exception of B<RANDFILE>, this is probably a bug and may +change in future releases. -The options for B<ca> are contained in the B<ca> section of the -configuration file. Many of these are identical to command line +Many of the configuration file options are identical to command line options. Where the option is present in the configuration file and the command line the command line value is used. Where an option is described as mandatory then it must be present in -- Bodo Möller <[EMAIL PROTECTED]> PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html * TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt * Tel. +49-6151-16-6628, Fax +49-6151-16-6036 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
