openssl-ca.pod.in - OpenGrok cross reference for /openssl/doc/man1/openssl-ca.pod.in

Lines Matching refs:same
219 (see the configuration option B<database>), and uses the same
235 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
236 YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In
243 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
244 YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In
282 Normally the DN order of a certificate is the same as the order of the
284 is the same as the request. This is largely for compatibility with the
376 YYMMDDHHMMSSZ format (the same as an ASN1 UTCTime structure) or
377 YYYYMMDDHHMMSSZ format (the same as an ASN1 GeneralizedTime structure).
383 and B<-crlsec> are ignored. Accepts times in the same formats as
440 This is the same as B<crl_compromise> except the revocation reason is set to
492 and long names are the same when this option is used.
496 The same as the B<-outdir> command line option. It specifies
501 The same as B<-cert>. It gives the file containing the CA
517 The same as the B<-days> option. The number of days from today to certify
522 The same as the B<-startdate> option. The start date to certify
527 The same as the B<-enddate> option. Either this option or
533 The same as the B<-crlhours> and the B<-crldays> options. These
539 The same as the B<-md> option. Mandatory except where the signing algorithm does
551 several valid certificate entries may have the exact same subject.
582 The same as B<-preserveDN>
586 The same as B<-noemailDN>. If you want the EMAIL field to be removed
592 The same as B<-msie_hack>
596 The same as B<-policy>. Mandatory. See the B<POLICY FORMAT> section
636 must match the same field in the CA certificate. If the value is
651 If you need to include the same component twice then it can be
807 command on the same database can have unpredictable results.