Lines Matching refs:command
71 This command emulates a CA application.
84 The descriptions of the B<ca> command options are divided into each purpose.
185 systems the command line arguments are visible (e.g., when using
239 Any digest supported by the L<openssl-dgst(1)> command can be used. For signing
252 This is a deprecated option to make this command work with very old versions
436 The section of the configuration file containing options for this command
437 is found as follows: If the B<-name> command line option is used,
449 Many of the configuration file options are identical to command line
451 and the command line the command line value is used. Where an
453 the configuration file or the command line equivalent (if
474 The same as the B<-outdir> command line option. It specifies
506 B<default_days> (or the command line equivalents) must be
512 will only be used if neither command line option is present. At
533 the B<-selfsign> command line option.
622 The input to the B<-spkac> command line option is a Netscape
638 Note: these examples assume that the directory structure this command
686 A sample configuration file with the relevant sections for this command:
724 configuration file entries, environment variables or command line options.
751 This command is quirky and at times downright unfriendly.
757 This command really needs rewriting or the required functionality
758 exposed at either a command or interface level so that a more user-friendly
774 This command was originally meant as an example of how to do things in a CA.
783 This command command is effectively a single user command: no locking
785 command on the same database can have unpredictable results.