openssl-ca.pod.in 28 KB

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