1 .\" Automatically generated by Pod::Man version 1.15
2 .\" Wed Feb 19 16:49:31 2003
5 .\" ======================================================================
6 .de Sh \" Subsection heading
14 .de Sp \" Vertical space (when we can't use .PP)
20 .ie \\n(.$>=3 .ne \\$3
24 .de Vb \" Begin verbatim text
29 .de Ve \" End verbatim text
34 .\" Set up some character translations and predefined strings. \*(-- will
35 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
36 .\" double quote, and \*(R" will give a right double quote. | will give a
37 .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used
38 .\" to do unbreakable dashes and therefore won't be available. \*(C` and
39 .\" \*(C' expand to `' in nroff, nothing in troff, for use with C<>
41 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
45 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
46 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
59 .\" If the F register is turned on, we'll generate index entries on stderr
60 .\" for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and
61 .\" index entries marked with X<> in POD. Of course, you'll have to process
62 .\" the output yourself in some meaningful fashion.
65 . tm Index:\\$1\t\\n%\t"\\$2"
71 .\" For nroff, turn off justification. Always turn off hyphenation; it
72 .\" makes way too many mistakes in technical documents.
76 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
77 .\" Fear. Run. Save yourself. No user-serviceable parts.
79 . \" fudge factors for nroff and troff
88 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
94 . \" simple accents for nroff and troff
104 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
105 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
106 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
107 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
108 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
109 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
111 . \" troff and (daisy-wheel) nroff accents
112 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
113 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
114 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
115 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
116 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
117 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
118 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
119 .ds ae a\h'-(\w'a'u*4/10)'e
120 .ds Ae A\h'-(\w'A'u*4/10)'E
121 . \" corrections for vroff
122 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
123 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
124 . \" for low resolution devices (crt and lpr)
125 .if \n(.H>23 .if \n(.V>19 \
138 .\" ======================================================================
141 .TH CA 1 "0.9.7a" "2003-02-19" "OpenSSL"
144 ca \- sample minimal \s-1CA\s0 application
146 .IX Header "SYNOPSIS"
147 \&\fBopenssl\fR \fBca\fR
149 [\fB\-config filename\fR]
150 [\fB\-name section\fR]
152 [\fB\-revoke file\fR]
153 [\fB\-crl_reason reason\fR]
154 [\fB\-crl_hold instruction\fR]
155 [\fB\-crl_compromise time\fR]
156 [\fB\-crl_CA_compromise time\fR]
158 [\fB\-crldays days\fR]
159 [\fB\-crlhours hours\fR]
160 [\fB\-crlexts section\fR]
161 [\fB\-startdate date\fR]
162 [\fB\-enddate date\fR]
166 [\fB\-keyfile arg\fR]
176 [\fB\-ss_cert file\fR]
181 [\fB\-extensions section\fR]
182 [\fB\-extfile section\fR]
185 .IX Header "DESCRIPTION"
186 The \fBca\fR command is a minimal \s-1CA\s0 application. It can be used
187 to sign certificate requests in a variety of forms and generate
188 CRLs it also maintains a text database of issued certificates
191 The options descriptions will be divided into each purpose.
193 .IX Header "CA OPTIONS"
194 .Ip "\fB\-config filename\fR" 4
195 .IX Item "-config filename"
196 specifies the configuration file to use.
197 .Ip "\fB\-name section\fR" 4
198 .IX Item "-name section"
199 specifies the configuration file section to use (overrides
200 \&\fBdefault_ca\fR in the \fBca\fR section).
201 .Ip "\fB\-in filename\fR" 4
202 .IX Item "-in filename"
203 an input filename containing a single certificate request to be
204 signed by the \s-1CA\s0.
205 .Ip "\fB\-ss_cert filename\fR" 4
206 .IX Item "-ss_cert filename"
207 a single self signed certificate to be signed by the \s-1CA\s0.
208 .Ip "\fB\-spkac filename\fR" 4
209 .IX Item "-spkac filename"
210 a file containing a single Netscape signed public key and challenge
211 and additional field values to be signed by the \s-1CA\s0. See the \fB\s-1SPKAC\s0 \s-1FORMAT\s0\fR
212 section for information on the required format.
213 .Ip "\fB\-infiles\fR" 4
215 if present this should be the last option, all subsequent arguments
216 are assumed to the the names of files containing certificate requests.
217 .Ip "\fB\-out filename\fR" 4
218 .IX Item "-out filename"
219 the output file to output certificates to. The default is standard
220 output. The certificate details will also be printed out to this
222 .Ip "\fB\-outdir directory\fR" 4
223 .IX Item "-outdir directory"
224 the directory to output certificates to. The certificate will be
225 written to a filename consisting of the serial number in hex with
226 \&\*(L".pem\*(R" appended.
229 the \s-1CA\s0 certificate file.
230 .Ip "\fB\-keyfile filename\fR" 4
231 .IX Item "-keyfile filename"
232 the private key to sign requests with.
233 .Ip "\fB\-key password\fR" 4
234 .IX Item "-key password"
235 the password used to encrypt the private key. Since on some
236 systems the command line arguments are visible (e.g. Unix with
237 the 'ps' utility) this option should be used with caution.
238 .Ip "\fB\-passin arg\fR" 4
239 .IX Item "-passin arg"
240 the key password source. For more information about the format of \fBarg\fR
241 see the \fB\s-1PASS\s0 \s-1PHRASE\s0 \s-1ARGUMENTS\s0\fR section in openssl(1).
242 .Ip "\fB\-verbose\fR" 4
244 this prints extra details about the operations being performed.
245 .Ip "\fB\-notext\fR" 4
247 don't output the text form of a certificate to the output file.
248 .Ip "\fB\-startdate date\fR" 4
249 .IX Item "-startdate date"
250 this allows the start date to be explicitly set. The format of the
251 date is \s-1YYMMDDHHMMSSZ\s0 (the same as an \s-1ASN1\s0 UTCTime structure).
252 .Ip "\fB\-enddate date\fR" 4
253 .IX Item "-enddate date"
254 this allows the expiry date to be explicitly set. The format of the
255 date is \s-1YYMMDDHHMMSSZ\s0 (the same as an \s-1ASN1\s0 UTCTime structure).
256 .Ip "\fB\-days arg\fR" 4
258 the number of days to certify the certificate for.
259 .Ip "\fB\-md alg\fR" 4
261 the message digest to use. Possible values include md5, sha1 and mdc2.
262 This option also applies to CRLs.
263 .Ip "\fB\-policy arg\fR" 4
264 .IX Item "-policy arg"
265 this option defines the \s-1CA\s0 \*(L"policy\*(R" to use. This is a section in
266 the configuration file which decides which fields should be mandatory
267 or match the \s-1CA\s0 certificate. Check out the \fB\s-1POLICY\s0 \s-1FORMAT\s0\fR section
268 for more information.
269 .Ip "\fB\-msie_hack\fR" 4
270 .IX Item "-msie_hack"
271 this is a legacy option to make \fBca\fR work with very old versions of
272 the \s-1IE\s0 certificate enrollment control \*(L"certenr3\*(R". It used UniversalStrings
273 for almost everything. Since the old control has various security bugs
274 its use is strongly discouraged. The newer control \*(L"Xenroll\*(R" does not
276 .Ip "\fB\-preserveDN\fR" 4
277 .IX Item "-preserveDN"
278 Normally the \s-1DN\s0 order of a certificate is the same as the order of the
279 fields in the relevant policy section. When this option is set the order
280 is the same as the request. This is largely for compatibility with the
281 older \s-1IE\s0 enrollment control which would only accept certificates if their
282 DNs match the order of the request. This is not needed for Xenroll.
283 .Ip "\fB\-noemailDN\fR" 4
284 .IX Item "-noemailDN"
285 The \s-1DN\s0 of a certificate can contain the \s-1EMAIL\s0 field if present in the
286 request \s-1DN\s0, however it is good policy just having the e-mail set into
287 the altName extension of the certificate. When this option is set the
288 \&\s-1EMAIL\s0 field is removed from the certificate' subject and set only in
289 the, eventually present, extensions. The \fBemail_in_dn\fR keyword can be
290 used in the configuration file to enable this behaviour.
291 .Ip "\fB\-batch\fR" 4
293 this sets the batch mode. In this mode no questions will be asked
294 and all certificates will be certified automatically.
295 .Ip "\fB\-extensions section\fR" 4
296 .IX Item "-extensions section"
297 the section of the configuration file containing certificate extensions
298 to be added when a certificate is issued (defaults to \fBx509_extensions\fR
299 unless the \fB\-extfile\fR option is used). If no extension section is
300 present then, a V1 certificate is created. If the extension section
301 is present (even if it is empty), then a V3 certificate is created.
302 .Ip "\fB\-extfile file\fR" 4
303 .IX Item "-extfile file"
304 an additional configuration file to read certificate extensions from
305 (using the default section unless the \fB\-extensions\fR option is also
307 .Ip "\fB\-engine id\fR" 4
308 .IX Item "-engine id"
309 specifying an engine (by it's unique \fBid\fR string) will cause \fBreq\fR
310 to attempt to obtain a functional reference to the specified engine,
311 thus initialising it if needed. The engine will then be set as the default
312 for all available algorithms.
314 .IX Header "CRL OPTIONS"
315 .Ip "\fB\-gencrl\fR" 4
317 this option generates a \s-1CRL\s0 based on information in the index file.
318 .Ip "\fB\-crldays num\fR" 4
319 .IX Item "-crldays num"
320 the number of days before the next \s-1CRL\s0 is due. That is the days from
321 now to place in the \s-1CRL\s0 nextUpdate field.
322 .Ip "\fB\-crlhours num\fR" 4
323 .IX Item "-crlhours num"
324 the number of hours before the next \s-1CRL\s0 is due.
325 .Ip "\fB\-revoke filename\fR" 4
326 .IX Item "-revoke filename"
327 a filename containing a certificate to revoke.
328 .Ip "\fB\-crl_reason reason\fR" 4
329 .IX Item "-crl_reason reason"
330 revocation reason, where \fBreason\fR is one of: \fBunspecified\fR, \fBkeyCompromise\fR,
331 \&\fBCACompromise\fR, \fBaffiliationChanged\fR, \fBsuperseded\fR, \fBcessationOfOperation\fR,
332 \&\fBcertificateHold\fR or \fBremoveFromCRL\fR. The matching of \fBreason\fR is case
333 insensitive. Setting any revocation reason will make the \s-1CRL\s0 v2.
335 In practive \fBremoveFromCRL\fR is not particularly useful because it is only used
336 in delta CRLs which are not currently implemented.
337 .Ip "\fB\-crl_hold instruction\fR" 4
338 .IX Item "-crl_hold instruction"
339 This sets the \s-1CRL\s0 revocation reason code to \fBcertificateHold\fR and the hold
340 instruction to \fBinstruction\fR which must be an \s-1OID\s0. Although any \s-1OID\s0 can be
341 used only \fBholdInstructionNone\fR (the use of which is discouraged by \s-1RFC2459\s0)
342 \&\fBholdInstructionCallIssuer\fR or \fBholdInstructionReject\fR will normally be used.
343 .Ip "\fB\-crl_compromise time\fR" 4
344 .IX Item "-crl_compromise time"
345 This sets the revocation reason to \fBkeyCompromise\fR and the compromise time to
346 \&\fBtime\fR. \fBtime\fR should be in GeneralizedTime format that is \fB\s-1YYYYMMDDHHMMSSZ\s0\fR.
347 .Ip "\fB\-crl_CA_compromise time\fR" 4
348 .IX Item "-crl_CA_compromise time"
349 This is the same as \fBcrl_compromise\fR except the revocation reason is set to
350 \&\fBCACompromise\fR.
351 .Ip "\fB\-subj arg\fR" 4
353 supersedes subject name given in the request.
354 The arg must be formatted as \fI/type0=value0/type1=value1/type2=...\fR,
355 characters may be escaped by \e (backslash), no spaces are skipped.
356 .Ip "\fB\-crlexts section\fR" 4
357 .IX Item "-crlexts section"
358 the section of the configuration file containing \s-1CRL\s0 extensions to
359 include. If no \s-1CRL\s0 extension section is present then a V1 \s-1CRL\s0 is
360 created, if the \s-1CRL\s0 extension section is present (even if it is
361 empty) then a V2 \s-1CRL\s0 is created. The \s-1CRL\s0 extensions specified are
362 \&\s-1CRL\s0 extensions and \fBnot\fR \s-1CRL\s0 entry extensions. It should be noted
363 that some software (for example Netscape) can't handle V2 CRLs.
364 .SH "CONFIGURATION FILE OPTIONS"
365 .IX Header "CONFIGURATION FILE OPTIONS"
366 The section of the configuration file containing options for \fBca\fR
367 is found as follows: If the \fB\-name\fR command line option is used,
368 then it names the section to be used. Otherwise the section to
369 be used must be named in the \fBdefault_ca\fR option of the \fBca\fR section
370 of the configuration file (or in the default section of the
371 configuration file). Besides \fBdefault_ca\fR, the following options are
372 read directly from the \fBca\fR section:
376 With the exception of \fB\s-1RANDFILE\s0\fR, this is probably a bug and may
377 change in future releases.
379 Many of the configuration file options are identical to command line
380 options. Where the option is present in the configuration file
381 and the command line the command line value is used. Where an
382 option is described as mandatory then it must be present in
383 the configuration file or the command line equivalent (if
385 .Ip "\fBoid_file\fR" 4
387 This specifies a file containing additional \fB\s-1OBJECT\s0 \s-1IDENTIFIERS\s0\fR.
388 Each line of the file should consist of the numerical form of the
389 object identifier followed by white space then the short name followed
390 by white space and finally the long name.
391 .Ip "\fBoid_section\fR" 4
392 .IX Item "oid_section"
393 This specifies a section in the configuration file containing extra
394 object identifiers. Each line should consist of the short name of the
395 object identifier followed by \fB=\fR and the numerical form. The short
396 and long names are the same when this option is used.
397 .Ip "\fBnew_certs_dir\fR" 4
398 .IX Item "new_certs_dir"
399 the same as the \fB\-outdir\fR command line option. It specifies
400 the directory where new certificates will be placed. Mandatory.
401 .Ip "\fBcertificate\fR" 4
402 .IX Item "certificate"
403 the same as \fB\-cert\fR. It gives the file containing the \s-1CA\s0
404 certificate. Mandatory.
405 .Ip "\fBprivate_key\fR" 4
406 .IX Item "private_key"
407 same as the \fB\-keyfile\fR option. The file containing the
408 \&\s-1CA\s0 private key. Mandatory.
409 .Ip "\fB\s-1RANDFILE\s0\fR" 4
411 a file used to read and write random number seed information, or
412 an \s-1EGD\s0 socket (see RAND_egd(3)).
413 .Ip "\fBdefault_days\fR" 4
414 .IX Item "default_days"
415 the same as the \fB\-days\fR option. The number of days to certify
417 .Ip "\fBdefault_startdate\fR" 4
418 .IX Item "default_startdate"
419 the same as the \fB\-startdate\fR option. The start date to certify
420 a certificate for. If not set the current time is used.
421 .Ip "\fBdefault_enddate\fR" 4
422 .IX Item "default_enddate"
423 the same as the \fB\-enddate\fR option. Either this option or
424 \&\fBdefault_days\fR (or the command line equivalents) must be
426 .Ip "\fBdefault_crl_hours default_crl_days\fR" 4
427 .IX Item "default_crl_hours default_crl_days"
428 the same as the \fB\-crlhours\fR and the \fB\-crldays\fR options. These
429 will only be used if neither command line option is present. At
430 least one of these must be present to generate a \s-1CRL\s0.
431 .Ip "\fBdefault_md\fR" 4
432 .IX Item "default_md"
433 the same as the \fB\-md\fR option. The message digest to use. Mandatory.
434 .Ip "\fBdatabase\fR" 4
436 the text database file to use. Mandatory. This file must be present
437 though initially it will be empty.
438 .Ip "\fBserialfile\fR" 4
439 .IX Item "serialfile"
440 a text file containing the next serial number to use in hex. Mandatory.
441 This file must be present and contain a valid serial number.
442 .Ip "\fBx509_extensions\fR" 4
443 .IX Item "x509_extensions"
444 the same as \fB\-extensions\fR.
445 .Ip "\fBcrl_extensions\fR" 4
446 .IX Item "crl_extensions"
447 the same as \fB\-crlexts\fR.
448 .Ip "\fBpreserve\fR" 4
450 the same as \fB\-preserveDN\fR
451 .Ip "\fBemail_in_dn\fR" 4
452 .IX Item "email_in_dn"
453 the same as \fB\-noemailDN\fR. If you want the \s-1EMAIL\s0 field to be removed
454 from the \s-1DN\s0 of the certificate simply set this to 'no'. If not present
455 the default is to allow for the \s-1EMAIL\s0 filed in the certificate's \s-1DN\s0.
456 .Ip "\fBmsie_hack\fR" 4
458 the same as \fB\-msie_hack\fR
461 the same as \fB\-policy\fR. Mandatory. See the \fB\s-1POLICY\s0 \s-1FORMAT\s0\fR section
462 for more information.
463 .Ip "\fBnameopt\fR, \fBcertopt\fR" 4
464 .IX Item "nameopt, certopt"
465 these options allow the format used to display the certificate details
466 when asking the user to confirm signing. All the options supported by
467 the \fBx509\fR utilities \fB\-nameopt\fR and \fB\-certopt\fR switches can be used
468 here, except the \fBno_signame\fR and \fBno_sigdump\fR are permanently set
469 and cannot be disabled (this is because the certificate signature cannot
470 be displayed because the certificate has not been signed at this point).
472 For convenience the values \fBdefault_ca\fR are accepted by both to produce
475 If neither option is present the format used in earlier versions of
476 OpenSSL is used. Use of the old format is \fBstrongly\fR discouraged because
477 it only displays fields mentioned in the \fBpolicy\fR section, mishandles
478 multicharacter string types and does not display extensions.
479 .Ip "\fBcopy_extensions\fR" 4
480 .IX Item "copy_extensions"
481 determines how extensions in certificate requests should be handled.
482 If set to \fBnone\fR or this option is not present then extensions are
483 ignored and not copied to the certificate. If set to \fBcopy\fR then any
484 extensions present in the request that are not already present are copied
485 to the certificate. If set to \fBcopyall\fR then all extensions in the
486 request are copied to the certificate: if the extension is already present
487 in the certificate it is deleted first. See the \fB\s-1WARNINGS\s0\fR section before
490 The main use of this option is to allow a certificate request to supply
491 values for certain extensions such as subjectAltName.
493 .IX Header "POLICY FORMAT"
494 The policy section consists of a set of variables corresponding to
495 certificate \s-1DN\s0 fields. If the value is \*(L"match\*(R" then the field value
496 must match the same field in the \s-1CA\s0 certificate. If the value is
497 \&\*(L"supplied\*(R" then it must be present. If the value is \*(L"optional\*(R" then
498 it may be present. Any fields not mentioned in the policy section
499 are silently deleted, unless the \fB\-preserveDN\fR option is set but
500 this can be regarded more of a quirk than intended behaviour.
502 .IX Header "SPKAC FORMAT"
503 The input to the \fB\-spkac\fR command line option is a Netscape
504 signed public key and challenge. This will usually come from
505 the \fB\s-1KEYGEN\s0\fR tag in an \s-1HTML\s0 form to create a new private key.
506 It is however possible to create SPKACs using the \fBspkac\fR utility.
508 The file should contain the variable \s-1SPKAC\s0 set to the value of
509 the \s-1SPKAC\s0 and also the required \s-1DN\s0 components as name value pairs.
510 If you need to include the same component twice then it can be
511 preceded by a number and a '.'.
513 .IX Header "EXAMPLES"
514 Note: these examples assume that the \fBca\fR directory structure is
515 already set up and the relevant files already exist. This usually
516 involves creating a \s-1CA\s0 certificate and private key with \fBreq\fR, a
517 serial number file and an empty index file and placing them in
518 the relevant directories.
520 To use the sample configuration file below the directories demoCA,
521 demoCA/private and demoCA/newcerts would be created. The \s-1CA\s0
522 certificate would be copied to demoCA/cacert.pem and its private
523 key to demoCA/private/cakey.pem. A file demoCA/serial would be
524 created containing for example \*(L"01\*(R" and the empty index file
527 Sign a certificate request:
530 \& openssl ca -in req.pem -out newcert.pem
532 Sign a certificate request, using \s-1CA\s0 extensions:
535 \& openssl ca -in req.pem -extensions v3_ca -out newcert.pem
537 Generate a \s-1CRL\s0
540 \& openssl ca -gencrl -out crl.pem
542 Sign several requests:
545 \& openssl ca -infiles req1.pem req2.pem req3.pem
547 Certify a Netscape \s-1SPKAC:\s0
550 \& openssl ca -spkac spkac.txt
552 A sample \s-1SPKAC\s0 file (the \s-1SPKAC\s0 line has been truncated for clarity):
555 \& SPKAC=MIG0MGAwXDANBgkqhkiG9w0BAQEFAANLADBIAkEAn7PDhCeV/xIxUg8V70YRxK2A5
557 \& emailAddress=steve@openssl.org
558 \& 0.OU=OpenSSL Group
559 \& 1.OU=Another Group
561 A sample configuration file with the relevant sections for \fBca\fR:
565 \& default_ca = CA_default # The default ca section
571 \& dir = ./demoCA # top dir
572 \& database = $dir/index.txt # index file.
573 \& new_certs_dir = $dir/newcerts # new certs dir
576 \& certificate = $dir/cacert.pem # The CA cert
577 \& serial = $dir/serial # serial no file
578 \& private_key = $dir/private/cakey.pem# CA private key
579 \& RANDFILE = $dir/private/.rand # random number file
582 \& default_days = 365 # how long to certify for
583 \& default_crl_days= 30 # how long before next CRL
584 \& default_md = md5 # md to use
587 \& policy = policy_any # default policy
588 \& email_in_dn = no # Don't add the email into cert DN
591 \& nameopt = default_ca # Subject name display option
592 \& certopt = default_ca # Certificate display option
593 \& copy_extensions = none # Don't copy extensions from request
597 \& countryName = supplied
598 \& stateOrProvinceName = optional
599 \& organizationName = optional
600 \& organizationalUnitName = optional
601 \& commonName = supplied
602 \& emailAddress = optional
606 Note: the location of all files can change either by compile time options,
607 configuration file entries, environment variables or command line options.
608 The values below reflect the default values.
611 \& /usr/local/ssl/lib/openssl.cnf - master configuration file
612 \& ./demoCA - main CA directory
613 \& ./demoCA/cacert.pem - CA certificate
614 \& ./demoCA/private/cakey.pem - CA private key
615 \& ./demoCA/serial - CA serial number file
616 \& ./demoCA/serial.old - CA serial number backup file
617 \& ./demoCA/index.txt - CA text database file
618 \& ./demoCA/index.txt.old - CA text database backup file
619 \& ./demoCA/certs - certificate output file
620 \& ./demoCA/.rnd - CA random seed information
622 .SH "ENVIRONMENT VARIABLES"
623 .IX Header "ENVIRONMENT VARIABLES"
624 \&\fB\s-1OPENSSL_CONF\s0\fR reflects the location of master configuration file it can
625 be overridden by the \fB\-config\fR command line option.
627 .IX Header "RESTRICTIONS"
628 The text database index file is a critical part of the process and
629 if corrupted it can be difficult to fix. It is theoretically possible
630 to rebuild the index file from all the issued certificates and a current
631 \&\s-1CRL:\s0 however there is no option to do this.
633 V2 \s-1CRL\s0 features like delta \s-1CRL\s0 support and \s-1CRL\s0 numbers are not currently
636 Although several requests can be input and handled at once it is only
637 possible to include one \s-1SPKAC\s0 or self signed certificate.
640 The use of an in memory text database can cause problems when large
641 numbers of certificates are present because, as the name implies
642 the database has to be kept in memory.
644 It is not possible to certify two certificates with the same \s-1DN:\s0 this
645 is a side effect of how the text database is indexed and it cannot easily
646 be fixed without introducing other problems. Some S/MIME clients can use
647 two certificates with the same \s-1DN\s0 for separate signing and encryption
650 The \fBca\fR command really needs rewriting or the required functionality
651 exposed at either a command or interface level so a more friendly utility
652 (perl script or \s-1GUI\s0) can handle things properly. The scripts \fB\s-1CA\s0.sh\fR and
653 \&\fB\s-1CA\s0.pl\fR help a little but not very much.
655 Any fields in a request that are not present in a policy are silently
656 deleted. This does not happen if the \fB\-preserveDN\fR option is used. To
657 enforce the absence of the \s-1EMAIL\s0 field within the \s-1DN\s0, as suggested by
658 RFCs, regardless the contents of the request' subject the \fB\-noemailDN\fR
659 option can be used. The behaviour should be more friendly and
662 Cancelling some commands by refusing to certify a certificate can
663 create an empty file.
665 .IX Header "WARNINGS"
666 The \fBca\fR command is quirky and at times downright unfriendly.
668 The \fBca\fR utility was originally meant as an example of how to do things
669 in a \s-1CA\s0. It was not supposed to be used as a full blown \s-1CA\s0 itself:
670 nevertheless some people are using it for this purpose.
672 The \fBca\fR command is effectively a single user command: no locking is
673 done on the various files and attempts to run more than one \fBca\fR command
674 on the same database can have unpredictable results.
676 The \fBcopy_extensions\fR option should be used with caution. If care is
677 not taken then it can be a security risk. For example if a certificate
678 request contains a basicConstraints extension with \s-1CA:TRUE\s0 and the
679 \&\fBcopy_extensions\fR value is set to \fBcopyall\fR and the user does not spot
680 this when the certificate is displayed then this will hand the requestor
681 a valid \s-1CA\s0 certificate.
683 This situation can be avoided by setting \fBcopy_extensions\fR to \fBcopy\fR
684 and including basicConstraints with \s-1CA:FALSE\s0 in the configuration file.
685 Then if the request contains a basicConstraints extension it will be
688 It is advisable to also include values for other extensions such
689 as \fBkeyUsage\fR to prevent a request supplying its own values.
691 Additional restrictions can be placed on the \s-1CA\s0 certificate itself.
692 For example if the \s-1CA\s0 certificate has:
695 \& basicConstraints = CA:TRUE, pathlen:0
697 then even if a certificate is issued with \s-1CA:TRUE\s0 it will not be valid.
699 .IX Header "SEE ALSO"
700 req(1), spkac(1), x509(1), CA.pl(1),
projects / dragonfly.git / blob