ca.pod 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760
  1. =pod
  2. =head1 NAME
  3. openssl-ca,
  4. ca - sample minimal CA application
  5. =head1 SYNOPSIS
  6. B<openssl> B<ca>
  7. [B<-help>]
  8. [B<-verbose>]
  9. [B<-config filename>]
  10. [B<-name section>]
  11. [B<-gencrl>]
  12. [B<-revoke file>]
  13. [B<-valid file>]
  14. [B<-status serial>]
  15. [B<-updatedb>]
  16. [B<-crl_reason reason>]
  17. [B<-crl_hold instruction>]
  18. [B<-crl_compromise time>]
  19. [B<-crl_CA_compromise time>]
  20. [B<-crldays days>]
  21. [B<-crlhours hours>]
  22. [B<-crlexts section>]
  23. [B<-startdate date>]
  24. [B<-enddate date>]
  25. [B<-days arg>]
  26. [B<-md arg>]
  27. [B<-policy arg>]
  28. [B<-keyfile arg>]
  29. [B<-keyform PEM|DER>]
  30. [B<-key arg>]
  31. [B<-passin arg>]
  32. [B<-cert file>]
  33. [B<-selfsign>]
  34. [B<-in file>]
  35. [B<-out file>]
  36. [B<-notext>]
  37. [B<-outdir dir>]
  38. [B<-infiles>]
  39. [B<-spkac file>]
  40. [B<-ss_cert file>]
  41. [B<-preserveDN>]
  42. [B<-noemailDN>]
  43. [B<-batch>]
  44. [B<-msie_hack>]
  45. [B<-extensions section>]
  46. [B<-extfile section>]
  47. [B<-engine id>]
  48. [B<-subj arg>]
  49. [B<-utf8>]
  50. [B<-create_serial>]
  51. [B<-rand_serial>]
  52. [B<-multivalue-rdn>]
  53. [B<-rand file...>]
  54. [B<-writerand file>]
  55. =head1 DESCRIPTION
  56. The B<ca> command is a minimal CA application. It can be used
  57. to sign certificate requests in a variety of forms and generate
  58. CRLs it also maintains a text database of issued certificates
  59. and their status.
  60. The options descriptions will be divided into each purpose.
  61. =head1 OPTIONS
  62. =over 4
  63. =item B<-help>
  64. Print out a usage message.
  65. =item B<-verbose>
  66. This prints extra details about the operations being performed.
  67. =item B<-config filename>
  68. Specifies the configuration file to use.
  69. Optional; for a description of the default value,
  70. see L<openssl(1)/COMMAND SUMMARY>.
  71. =item B<-name section>
  72. Specifies the configuration file section to use (overrides
  73. B<default_ca> in the B<ca> section).
  74. =item B<-in filename>
  75. An input filename containing a single certificate request to be
  76. signed by the CA.
  77. =item B<-ss_cert filename>
  78. A single self-signed certificate to be signed by the CA.
  79. =item B<-spkac filename>
  80. A file containing a single Netscape signed public key and challenge
  81. and additional field values to be signed by the CA. See the B<SPKAC FORMAT>
  82. section for information on the required input and output format.
  83. =item B<-infiles>
  84. If present this should be the last option, all subsequent arguments
  85. are taken as the names of files containing certificate requests.
  86. =item B<-out filename>
  87. The output file to output certificates to. The default is standard
  88. output. The certificate details will also be printed out to this
  89. file in PEM format (except that B<-spkac> outputs DER format).
  90. =item B<-outdir directory>
  91. The directory to output certificates to. The certificate will be
  92. written to a filename consisting of the serial number in hex with
  93. ".pem" appended.
  94. =item B<-cert>
  95. The CA certificate file.
  96. =item B<-keyfile filename>
  97. The private key to sign requests with.
  98. =item B<-keyform PEM|DER>
  99. The format of the data in the private key file.
  100. The default is PEM.
  101. =item B<-key password>
  102. The password used to encrypt the private key. Since on some
  103. systems the command line arguments are visible (e.g. Unix with
  104. the 'ps' utility) this option should be used with caution.
  105. =item B<-selfsign>
  106. Indicates the issued certificates are to be signed with the key
  107. the certificate requests were signed with (given with B<-keyfile>).
  108. Certificate requests signed with a different key are ignored. If
  109. B<-spkac>, B<-ss_cert> or B<-gencrl> are given, B<-selfsign> is
  110. ignored.
  111. A consequence of using B<-selfsign> is that the self-signed
  112. certificate appears among the entries in the certificate database
  113. (see the configuration option B<database>), and uses the same
  114. serial number counter as all other certificates sign with the
  115. self-signed certificate.
  116. =item B<-passin arg>
  117. The key password source. For more information about the format of B<arg>
  118. see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)>.
  119. =item B<-notext>
  120. Don't output the text form of a certificate to the output file.
  121. =item B<-startdate date>
  122. This allows the start date to be explicitly set. The format of the
  123. date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
  124. YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In
  125. both formats, seconds SS and timezone Z must be present.
  126. =item B<-enddate date>
  127. This allows the expiry date to be explicitly set. The format of the
  128. date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
  129. YYYYMMDDHHMMSSZ (the same as an ASN1 GeneralizedTime structure). In
  130. both formats, seconds SS and timezone Z must be present.
  131. =item B<-days arg>
  132. The number of days to certify the certificate for.
  133. =item B<-md alg>
  134. The message digest to use.
  135. Any digest supported by the OpenSSL B<dgst> command can be used. If the signing
  136. key is using Ed25519 or Ed448 then you should specify "null" for the digest.
  137. This option also applies to CRLs.
  138. =item B<-policy arg>
  139. This option defines the CA "policy" to use. This is a section in
  140. the configuration file which decides which fields should be mandatory
  141. or match the CA certificate. Check out the B<POLICY FORMAT> section
  142. for more information.
  143. =item B<-msie_hack>
  144. This is a deprecated option to make B<ca> work with very old versions of
  145. the IE certificate enrollment control "certenr3". It used UniversalStrings
  146. for almost everything. Since the old control has various security bugs
  147. its use is strongly discouraged.
  148. =item B<-preserveDN>
  149. Normally the DN order of a certificate is the same as the order of the
  150. fields in the relevant policy section. When this option is set the order
  151. is the same as the request. This is largely for compatibility with the
  152. older IE enrollment control which would only accept certificates if their
  153. DNs match the order of the request. This is not needed for Xenroll.
  154. =item B<-noemailDN>
  155. The DN of a certificate can contain the EMAIL field if present in the
  156. request DN, however it is good policy just having the e-mail set into
  157. the altName extension of the certificate. When this option is set the
  158. EMAIL field is removed from the certificate' subject and set only in
  159. the, eventually present, extensions. The B<email_in_dn> keyword can be
  160. used in the configuration file to enable this behaviour.
  161. =item B<-batch>
  162. This sets the batch mode. In this mode no questions will be asked
  163. and all certificates will be certified automatically.
  164. =item B<-extensions section>
  165. The section of the configuration file containing certificate extensions
  166. to be added when a certificate is issued (defaults to B<x509_extensions>
  167. unless the B<-extfile> option is used). If no extension section is
  168. present then, a V1 certificate is created. If the extension section
  169. is present (even if it is empty), then a V3 certificate is created. See the:w
  170. L<x509v3_config(5)> manual page for details of the
  171. extension section format.
  172. =item B<-extfile file>
  173. An additional configuration file to read certificate extensions from
  174. (using the default section unless the B<-extensions> option is also
  175. used).
  176. =item B<-engine id>
  177. Specifying an engine (by its unique B<id> string) will cause B<ca>
  178. to attempt to obtain a functional reference to the specified engine,
  179. thus initialising it if needed. The engine will then be set as the default
  180. for all available algorithms.
  181. =item B<-subj arg>
  182. Supersedes subject name given in the request.
  183. The arg must be formatted as I</type0=value0/type1=value1/type2=...>,
  184. characters may be escaped by \ (backslash), no spaces are skipped.
  185. =item B<-utf8>
  186. This option causes field values to be interpreted as UTF8 strings, by
  187. default they are interpreted as ASCII. This means that the field
  188. values, whether prompted from a terminal or obtained from a
  189. configuration file, must be valid UTF8 strings.
  190. =item B<-create_serial>
  191. If reading serial from the text file as specified in the configuration
  192. fails, specifying this option creates a new random serial to be used as next
  193. serial number.
  194. To get random serial numbers, use the B<-rand_serial> flag instead; this
  195. should only be used for simple error-recovery.
  196. =item B<-rand_serial>
  197. Generate a large random number to use as the serial number.
  198. This overrides any option or configuration to use a serial number file.
  199. =item B<-multivalue-rdn>
  200. This option causes the -subj argument to be interpreted with full
  201. support for multivalued RDNs. Example:
  202. I</DC=org/DC=OpenSSL/DC=users/UID=123456+CN=John Doe>
  203. If -multi-rdn is not used then the UID value is I<123456+CN=John Doe>.
  204. =item B<-rand file...>
  205. A file or files containing random data used to seed the random number
  206. generator.
  207. Multiple files can be specified separated by an OS-dependent character.
  208. The separator is B<;> for MS-Windows, B<,> for OpenVMS, and B<:> for
  209. all others.
  210. =item [B<-writerand file>]
  211. Writes random data to the specified I<file> upon exit.
  212. This can be used with a subsequent B<-rand> flag.
  213. =back
  214. =head1 CRL OPTIONS
  215. =over 4
  216. =item B<-gencrl>
  217. This option generates a CRL based on information in the index file.
  218. =item B<-crldays num>
  219. The number of days before the next CRL is due. That is the days from
  220. now to place in the CRL nextUpdate field.
  221. =item B<-crlhours num>
  222. The number of hours before the next CRL is due.
  223. =item B<-revoke filename>
  224. A filename containing a certificate to revoke.
  225. =item B<-valid filename>
  226. A filename containing a certificate to add a Valid certificate entry.
  227. =item B<-status serial>
  228. Displays the revocation status of the certificate with the specified
  229. serial number and exits.
  230. =item B<-updatedb>
  231. Updates the database index to purge expired certificates.
  232. =item B<-crl_reason reason>
  233. Revocation reason, where B<reason> is one of: B<unspecified>, B<keyCompromise>,
  234. B<CACompromise>, B<affiliationChanged>, B<superseded>, B<cessationOfOperation>,
  235. B<certificateHold> or B<removeFromCRL>. The matching of B<reason> is case
  236. insensitive. Setting any revocation reason will make the CRL v2.
  237. In practice B<removeFromCRL> is not particularly useful because it is only used
  238. in delta CRLs which are not currently implemented.
  239. =item B<-crl_hold instruction>
  240. This sets the CRL revocation reason code to B<certificateHold> and the hold
  241. instruction to B<instruction> which must be an OID. Although any OID can be
  242. used only B<holdInstructionNone> (the use of which is discouraged by RFC2459)
  243. B<holdInstructionCallIssuer> or B<holdInstructionReject> will normally be used.
  244. =item B<-crl_compromise time>
  245. This sets the revocation reason to B<keyCompromise> and the compromise time to
  246. B<time>. B<time> should be in GeneralizedTime format that is B<YYYYMMDDHHMMSSZ>.
  247. =item B<-crl_CA_compromise time>
  248. This is the same as B<crl_compromise> except the revocation reason is set to
  249. B<CACompromise>.
  250. =item B<-crlexts section>
  251. The section of the configuration file containing CRL extensions to
  252. include. If no CRL extension section is present then a V1 CRL is
  253. created, if the CRL extension section is present (even if it is
  254. empty) then a V2 CRL is created. The CRL extensions specified are
  255. CRL extensions and B<not> CRL entry extensions. It should be noted
  256. that some software (for example Netscape) can't handle V2 CRLs. See
  257. L<x509v3_config(5)> manual page for details of the
  258. extension section format.
  259. =back
  260. =head1 CONFIGURATION FILE OPTIONS
  261. The section of the configuration file containing options for B<ca>
  262. is found as follows: If the B<-name> command line option is used,
  263. then it names the section to be used. Otherwise the section to
  264. be used must be named in the B<default_ca> option of the B<ca> section
  265. of the configuration file (or in the default section of the
  266. configuration file). Besides B<default_ca>, the following options are
  267. read directly from the B<ca> section:
  268. RANDFILE
  269. preserve
  270. msie_hack
  271. With the exception of B<RANDFILE>, this is probably a bug and may
  272. change in future releases.
  273. Many of the configuration file options are identical to command line
  274. options. Where the option is present in the configuration file
  275. and the command line the command line value is used. Where an
  276. option is described as mandatory then it must be present in
  277. the configuration file or the command line equivalent (if
  278. any) used.
  279. =over 4
  280. =item B<oid_file>
  281. This specifies a file containing additional B<OBJECT IDENTIFIERS>.
  282. Each line of the file should consist of the numerical form of the
  283. object identifier followed by white space then the short name followed
  284. by white space and finally the long name.
  285. =item B<oid_section>
  286. This specifies a section in the configuration file containing extra
  287. object identifiers. Each line should consist of the short name of the
  288. object identifier followed by B<=> and the numerical form. The short
  289. and long names are the same when this option is used.
  290. =item B<new_certs_dir>
  291. The same as the B<-outdir> command line option. It specifies
  292. the directory where new certificates will be placed. Mandatory.
  293. =item B<certificate>
  294. The same as B<-cert>. It gives the file containing the CA
  295. certificate. Mandatory.
  296. =item B<private_key>
  297. Same as the B<-keyfile> option. The file containing the
  298. CA private key. Mandatory.
  299. =item B<RANDFILE>
  300. At startup the specified file is loaded into the random number generator,
  301. and at exit 256 bytes will be written to it.
  302. =item B<default_days>
  303. The same as the B<-days> option. The number of days to certify
  304. a certificate for.
  305. =item B<default_startdate>
  306. The same as the B<-startdate> option. The start date to certify
  307. a certificate for. If not set the current time is used.
  308. =item B<default_enddate>
  309. The same as the B<-enddate> option. Either this option or
  310. B<default_days> (or the command line equivalents) must be
  311. present.
  312. =item B<default_crl_hours default_crl_days>
  313. The same as the B<-crlhours> and the B<-crldays> options. These
  314. will only be used if neither command line option is present. At
  315. least one of these must be present to generate a CRL.
  316. =item B<default_md>
  317. The same as the B<-md> option. Mandatory.
  318. =item B<database>
  319. The text database file to use. Mandatory. This file must be present
  320. though initially it will be empty.
  321. =item B<unique_subject>
  322. If the value B<yes> is given, the valid certificate entries in the
  323. database must have unique subjects. if the value B<no> is given,
  324. several valid certificate entries may have the exact same subject.
  325. The default value is B<yes>, to be compatible with older (pre 0.9.8)
  326. versions of OpenSSL. However, to make CA certificate roll-over easier,
  327. it's recommended to use the value B<no>, especially if combined with
  328. the B<-selfsign> command line option.
  329. Note that it is valid in some circumstances for certificates to be created
  330. without any subject. In the case where there are multiple certificates without
  331. subjects this does not count as a duplicate.
  332. =item B<serial>
  333. A text file containing the next serial number to use in hex. Mandatory.
  334. This file must be present and contain a valid serial number.
  335. =item B<crlnumber>
  336. A text file containing the next CRL number to use in hex. The crl number
  337. will be inserted in the CRLs only if this file exists. If this file is
  338. present, it must contain a valid CRL number.
  339. =item B<x509_extensions>
  340. The same as B<-extensions>.
  341. =item B<crl_extensions>
  342. The same as B<-crlexts>.
  343. =item B<preserve>
  344. The same as B<-preserveDN>
  345. =item B<email_in_dn>
  346. The same as B<-noemailDN>. If you want the EMAIL field to be removed
  347. from the DN of the certificate simply set this to 'no'. If not present
  348. the default is to allow for the EMAIL filed in the certificate's DN.
  349. =item B<msie_hack>
  350. The same as B<-msie_hack>
  351. =item B<policy>
  352. The same as B<-policy>. Mandatory. See the B<POLICY FORMAT> section
  353. for more information.
  354. =item B<name_opt>, B<cert_opt>
  355. These options allow the format used to display the certificate details
  356. when asking the user to confirm signing. All the options supported by
  357. the B<x509> utilities B<-nameopt> and B<-certopt> switches can be used
  358. here, except the B<no_signame> and B<no_sigdump> are permanently set
  359. and cannot be disabled (this is because the certificate signature cannot
  360. be displayed because the certificate has not been signed at this point).
  361. For convenience the values B<ca_default> are accepted by both to produce
  362. a reasonable output.
  363. If neither option is present the format used in earlier versions of
  364. OpenSSL is used. Use of the old format is B<strongly> discouraged because
  365. it only displays fields mentioned in the B<policy> section, mishandles
  366. multicharacter string types and does not display extensions.
  367. =item B<copy_extensions>
  368. Determines how extensions in certificate requests should be handled.
  369. If set to B<none> or this option is not present then extensions are
  370. ignored and not copied to the certificate. If set to B<copy> then any
  371. extensions present in the request that are not already present are copied
  372. to the certificate. If set to B<copyall> then all extensions in the
  373. request are copied to the certificate: if the extension is already present
  374. in the certificate it is deleted first. See the B<WARNINGS> section before
  375. using this option.
  376. The main use of this option is to allow a certificate request to supply
  377. values for certain extensions such as subjectAltName.
  378. =back
  379. =head1 POLICY FORMAT
  380. The policy section consists of a set of variables corresponding to
  381. certificate DN fields. If the value is "match" then the field value
  382. must match the same field in the CA certificate. If the value is
  383. "supplied" then it must be present. If the value is "optional" then
  384. it may be present. Any fields not mentioned in the policy section
  385. are silently deleted, unless the B<-preserveDN> option is set but
  386. this can be regarded more of a quirk than intended behaviour.
  387. =head1 SPKAC FORMAT
  388. The input to the B<-spkac> command line option is a Netscape
  389. signed public key and challenge. This will usually come from
  390. the B<KEYGEN> tag in an HTML form to create a new private key.
  391. It is however possible to create SPKACs using the B<spkac> utility.
  392. The file should contain the variable SPKAC set to the value of
  393. the SPKAC and also the required DN components as name value pairs.
  394. If you need to include the same component twice then it can be
  395. preceded by a number and a '.'.
  396. When processing SPKAC format, the output is DER if the B<-out>
  397. flag is used, but PEM format if sending to stdout or the B<-outdir>
  398. flag is used.
  399. =head1 EXAMPLES
  400. Note: these examples assume that the B<ca> directory structure is
  401. already set up and the relevant files already exist. This usually
  402. involves creating a CA certificate and private key with B<req>, a
  403. serial number file and an empty index file and placing them in
  404. the relevant directories.
  405. To use the sample configuration file below the directories demoCA,
  406. demoCA/private and demoCA/newcerts would be created. The CA
  407. certificate would be copied to demoCA/cacert.pem and its private
  408. key to demoCA/private/cakey.pem. A file demoCA/serial would be
  409. created containing for example "01" and the empty index file
  410. demoCA/index.txt.
  411. Sign a certificate request:
  412. openssl ca -in req.pem -out newcert.pem
  413. Sign a certificate request, using CA extensions:
  414. openssl ca -in req.pem -extensions v3_ca -out newcert.pem
  415. Generate a CRL
  416. openssl ca -gencrl -out crl.pem
  417. Sign several requests:
  418. openssl ca -infiles req1.pem req2.pem req3.pem
  419. Certify a Netscape SPKAC:
  420. openssl ca -spkac spkac.txt
  421. A sample SPKAC file (the SPKAC line has been truncated for clarity):
  422. SPKAC=MIG0MGAwXDANBgkqhkiG9w0BAQEFAANLADBIAkEAn7PDhCeV/xIxUg8V70YRxK2A5
  423. CN=Steve Test
  424. emailAddress=steve@openssl.org
  425. 0.OU=OpenSSL Group
  426. 1.OU=Another Group
  427. A sample configuration file with the relevant sections for B<ca>:
  428. [ ca ]
  429. default_ca = CA_default # The default ca section
  430. [ CA_default ]
  431. dir = ./demoCA # top dir
  432. database = $dir/index.txt # index file.
  433. new_certs_dir = $dir/newcerts # new certs dir
  434. certificate = $dir/cacert.pem # The CA cert
  435. serial = $dir/serial # serial no file
  436. #rand_serial = yes # for random serial#'s
  437. private_key = $dir/private/cakey.pem# CA private key
  438. RANDFILE = $dir/private/.rand # random number file
  439. default_days = 365 # how long to certify for
  440. default_crl_days= 30 # how long before next CRL
  441. default_md = md5 # md to use
  442. policy = policy_any # default policy
  443. email_in_dn = no # Don't add the email into cert DN
  444. name_opt = ca_default # Subject name display option
  445. cert_opt = ca_default # Certificate display option
  446. copy_extensions = none # Don't copy extensions from request
  447. [ policy_any ]
  448. countryName = supplied
  449. stateOrProvinceName = optional
  450. organizationName = optional
  451. organizationalUnitName = optional
  452. commonName = supplied
  453. emailAddress = optional
  454. =head1 FILES
  455. Note: the location of all files can change either by compile time options,
  456. configuration file entries, environment variables or command line options.
  457. The values below reflect the default values.
  458. /usr/local/ssl/lib/openssl.cnf - master configuration file
  459. ./demoCA - main CA directory
  460. ./demoCA/cacert.pem - CA certificate
  461. ./demoCA/private/cakey.pem - CA private key
  462. ./demoCA/serial - CA serial number file
  463. ./demoCA/serial.old - CA serial number backup file
  464. ./demoCA/index.txt - CA text database file
  465. ./demoCA/index.txt.old - CA text database backup file
  466. ./demoCA/certs - certificate output file
  467. ./demoCA/.rnd - CA random seed information
  468. =head1 RESTRICTIONS
  469. The text database index file is a critical part of the process and
  470. if corrupted it can be difficult to fix. It is theoretically possible
  471. to rebuild the index file from all the issued certificates and a current
  472. CRL: however there is no option to do this.
  473. V2 CRL features like delta CRLs are not currently supported.
  474. Although several requests can be input and handled at once it is only
  475. possible to include one SPKAC or self-signed certificate.
  476. =head1 BUGS
  477. The use of an in-memory text database can cause problems when large
  478. numbers of certificates are present because, as the name implies
  479. the database has to be kept in memory.
  480. The B<ca> command really needs rewriting or the required functionality
  481. exposed at either a command or interface level so a more friendly utility
  482. (perl script or GUI) can handle things properly. The script
  483. B<CA.pl> helps a little but not very much.
  484. Any fields in a request that are not present in a policy are silently
  485. deleted. This does not happen if the B<-preserveDN> option is used. To
  486. enforce the absence of the EMAIL field within the DN, as suggested by
  487. RFCs, regardless the contents of the request' subject the B<-noemailDN>
  488. option can be used. The behaviour should be more friendly and
  489. configurable.
  490. Canceling some commands by refusing to certify a certificate can
  491. create an empty file.
  492. =head1 WARNINGS
  493. The B<ca> command is quirky and at times downright unfriendly.
  494. The B<ca> utility was originally meant as an example of how to do things
  495. in a CA. It was not supposed to be used as a full blown CA itself:
  496. nevertheless some people are using it for this purpose.
  497. The B<ca> command is effectively a single user command: no locking is
  498. done on the various files and attempts to run more than one B<ca> command
  499. on the same database can have unpredictable results.
  500. The B<copy_extensions> option should be used with caution. If care is
  501. not taken then it can be a security risk. For example if a certificate
  502. request contains a basicConstraints extension with CA:TRUE and the
  503. B<copy_extensions> value is set to B<copyall> and the user does not spot
  504. this when the certificate is displayed then this will hand the requester
  505. a valid CA certificate.
  506. This situation can be avoided by setting B<copy_extensions> to B<copy>
  507. and including basicConstraints with CA:FALSE in the configuration file.
  508. Then if the request contains a basicConstraints extension it will be
  509. ignored.
  510. It is advisable to also include values for other extensions such
  511. as B<keyUsage> to prevent a request supplying its own values.
  512. Additional restrictions can be placed on the CA certificate itself.
  513. For example if the CA certificate has:
  514. basicConstraints = CA:TRUE, pathlen:0
  515. then even if a certificate is issued with CA:TRUE it will not be valid.
  516. =head1 HISTORY
  517. Since OpenSSL 1.1.1, the program follows RFC5280. Specifically,
  518. certificate validity period (specified by any of B<-startdate>,
  519. B<-enddate> and B<-days>) will be encoded as UTCTime if the dates are
  520. earlier than year 2049 (included), and as GeneralizedTime if the dates
  521. are in year 2050 or later.
  522. =head1 SEE ALSO
  523. L<req(1)>, L<spkac(1)>, L<x509(1)>, L<CA.pl(1)>,
  524. L<config(5)>, L<x509v3_config(5)>
  525. =head1 COPYRIGHT
  526. Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
  527. Licensed under the OpenSSL license (the "License"). You may not use
  528. this file except in compliance with the License. You can obtain a copy
  529. in the file LICENSE in the source distribution or at
  530. L<https://www.openssl.org/source/license.html>.
  531. =cut