Annotation of src/usr.bin/openssl/openssl.1, Revision 1.69
1.69 ! jmc 1: .\" $OpenBSD: openssl.1,v 1.68 2016/09/03 13:26:55 jmc Exp $
1.1 jsing 2: .\" ====================================================================
3: .\" Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved.
4: .\"
5: .\" Redistribution and use in source and binary forms, with or without
6: .\" modification, are permitted provided that the following conditions
7: .\" are met:
8: .\"
9: .\" 1. Redistributions of source code must retain the above copyright
10: .\" notice, this list of conditions and the following disclaimer.
11: .\"
12: .\" 2. Redistributions in binary form must reproduce the above copyright
13: .\" notice, this list of conditions and the following disclaimer in
14: .\" the documentation and/or other materials provided with the
15: .\" distribution.
16: .\"
17: .\" 3. All advertising materials mentioning features or use of this
18: .\" software must display the following acknowledgment:
19: .\" "This product includes software developed by the OpenSSL Project
20: .\" for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
21: .\"
22: .\" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
23: .\" endorse or promote products derived from this software without
24: .\" prior written permission. For written permission, please contact
25: .\" openssl-core@openssl.org.
26: .\"
27: .\" 5. Products derived from this software may not be called "OpenSSL"
28: .\" nor may "OpenSSL" appear in their names without prior written
29: .\" permission of the OpenSSL Project.
30: .\"
31: .\" 6. Redistributions of any form whatsoever must retain the following
32: .\" acknowledgment:
33: .\" "This product includes software developed by the OpenSSL Project
34: .\" for use in the OpenSSL Toolkit (http://www.openssl.org/)"
35: .\"
36: .\" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
37: .\" EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
38: .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
39: .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
40: .\" ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
41: .\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
42: .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
43: .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
44: .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
45: .\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
46: .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
47: .\" OF THE POSSIBILITY OF SUCH DAMAGE.
48: .\" ====================================================================
49: .\"
50: .\" This product includes cryptographic software written by Eric Young
51: .\" (eay@cryptsoft.com). This product includes software written by Tim
52: .\" Hudson (tjh@cryptsoft.com).
53: .\"
54: .\"
55: .\" Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
56: .\" All rights reserved.
57: .\"
58: .\" This package is an SSL implementation written
59: .\" by Eric Young (eay@cryptsoft.com).
60: .\" The implementation was written so as to conform with Netscapes SSL.
61: .\"
62: .\" This library is free for commercial and non-commercial use as long as
63: .\" the following conditions are aheared to. The following conditions
64: .\" apply to all code found in this distribution, be it the RC4, RSA,
65: .\" lhash, DES, etc., code; not just the SSL code. The SSL documentation
66: .\" included with this distribution is covered by the same copyright terms
67: .\" except that the holder is Tim Hudson (tjh@cryptsoft.com).
68: .\"
69: .\" Copyright remains Eric Young's, and as such any Copyright notices in
70: .\" the code are not to be removed.
71: .\" If this package is used in a product, Eric Young should be given attribution
72: .\" as the author of the parts of the library used.
73: .\" This can be in the form of a textual message at program startup or
74: .\" in documentation (online or textual) provided with the package.
75: .\"
76: .\" Redistribution and use in source and binary forms, with or without
77: .\" modification, are permitted provided that the following conditions
78: .\" are met:
79: .\" 1. Redistributions of source code must retain the copyright
80: .\" notice, this list of conditions and the following disclaimer.
81: .\" 2. Redistributions in binary form must reproduce the above copyright
82: .\" notice, this list of conditions and the following disclaimer in the
83: .\" documentation and/or other materials provided with the distribution.
84: .\" 3. All advertising materials mentioning features or use of this software
85: .\" must display the following acknowledgement:
86: .\" "This product includes cryptographic software written by
87: .\" Eric Young (eay@cryptsoft.com)"
88: .\" The word 'cryptographic' can be left out if the rouines from the library
89: .\" being used are not cryptographic related :-).
90: .\" 4. If you include any Windows specific code (or a derivative thereof) from
91: .\" the apps directory (application code) you must include an
92: .\" acknowledgement:
93: .\" "This product includes software written by Tim Hudson
94: .\" (tjh@cryptsoft.com)"
95: .\"
96: .\" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
97: .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
98: .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
99: .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
100: .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
101: .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
102: .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
103: .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
104: .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
105: .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
106: .\" SUCH DAMAGE.
107: .\"
108: .\" The licence and distribution terms for any publically available version or
109: .\" derivative of this code cannot be changed. i.e. this code cannot simply be
110: .\" copied and put under another distribution licence
111: .\" [including the GNU Public Licence.]
112: .\"
113: .\" OPENSSL
114: .\"
1.69 ! jmc 115: .Dd $Mdocdate: September 3 2016 $
1.1 jsing 116: .Dt OPENSSL 1
117: .Os
118: .Sh NAME
119: .Nm openssl
120: .Nd OpenSSL command line tool
121: .Sh SYNOPSIS
122: .Nm
123: .Cm command
124: .Op Ar command_opts
125: .Op Ar command_args
126: .Pp
127: .Nm
1.13 bentley 128: .Cm list-standard-commands |
129: .Cm list-message-digest-commands |
130: .Cm list-cipher-commands |
131: .Cm list-cipher-algorithms |
132: .Cm list-message-digest-algorithms |
1.1 jsing 133: .Cm list-public-key-algorithms
134: .Pp
135: .Nm
1.39 jmc 136: .Cm no- Ns Ar command
1.1 jsing 137: .Sh DESCRIPTION
138: .Nm OpenSSL
1.31 jmc 139: is a cryptography toolkit implementing the
140: Transport Layer Security
1.1 jsing 141: .Pq TLS v1
1.31 jmc 142: network protocol,
143: as well as related cryptography standards.
1.1 jsing 144: .Pp
145: The
146: .Nm
147: program is a command line tool for using the various
148: cryptography functions of
1.39 jmc 149: .Nm openssl Ns 's
1.33 jmc 150: crypto library from the shell.
1.1 jsing 151: .Pp
152: The pseudo-commands
153: .Cm list-standard-commands , list-message-digest-commands ,
154: and
155: .Cm list-cipher-commands
156: output a list
157: .Pq one entry per line
158: of the names of all standard commands, message digest commands,
159: or cipher commands, respectively, that are available in the present
160: .Nm
161: utility.
162: .Pp
163: The pseudo-commands
164: .Cm list-cipher-algorithms
165: and
166: .Cm list-message-digest-algorithms
167: list all cipher and message digest names,
168: one entry per line.
169: Aliases are listed as:
170: .Pp
1.33 jmc 171: .D1 from => to
1.1 jsing 172: .Pp
173: The pseudo-command
174: .Cm list-public-key-algorithms
175: lists all supported public key algorithms.
176: .Pp
177: The pseudo-command
1.39 jmc 178: .Cm no- Ns Ar command
1.1 jsing 179: tests whether a command of the
180: specified name is available.
1.39 jmc 181: If
182: .Ar command
183: does not exist,
1.1 jsing 184: it returns 0
185: and prints
1.39 jmc 186: .Cm no- Ns Ar command ;
1.1 jsing 187: otherwise it returns 1 and prints
1.39 jmc 188: .Ar command .
189: In both cases, the output goes to stdout and nothing is printed to stderr.
1.1 jsing 190: Additional command line arguments are always ignored.
191: Since for each cipher there is a command of the same name,
192: this provides an easy way for shell scripts to test for the
193: availability of ciphers in the
194: .Nm
195: program.
196: .Pp
197: .Sy Note :
1.39 jmc 198: .Cm no- Ns Ar command
1.1 jsing 199: is not able to detect pseudo-commands such as
200: .Cm quit ,
201: .Cm list- Ns Ar ... Ns Cm -commands ,
202: or
1.39 jmc 203: .Cm no- Ns Ar command
1.1 jsing 204: itself.
205: .Sh ASN1PARSE
206: .nr nS 1
207: .Nm "openssl asn1parse"
208: .Op Fl i
209: .Op Fl dlimit Ar number
210: .Op Fl dump
211: .Op Fl genconf Ar file
212: .Op Fl genstr Ar str
213: .Op Fl in Ar file
1.34 jmc 214: .Op Fl inform Cm der | pem | txt
1.1 jsing 215: .Op Fl length Ar number
216: .Op Fl noout
217: .Op Fl offset Ar number
218: .Op Fl oid Ar file
219: .Op Fl out Ar file
220: .Op Fl strparse Ar offset
221: .nr nS 0
222: .Pp
223: The
224: .Nm asn1parse
225: command is a diagnostic utility that can parse ASN.1 structures.
226: It can also be used to extract data from ASN.1 formatted data.
227: .Pp
228: The options are as follows:
229: .Bl -tag -width Ds
230: .It Fl dlimit Ar number
231: Dump the first
232: .Ar number
233: bytes of unknown data in hex form.
234: .It Fl dump
235: Dump unknown data in hex form.
236: .It Fl genconf Ar file , Fl genstr Ar str
237: Generate encoded data based on string
238: .Ar str ,
239: file
240: .Ar file ,
1.34 jmc 241: or both, using the format described in
242: .Xr ASN1_generate_nconf 3 .
1.1 jsing 243: If only
244: .Ar file
245: is present then the string is obtained from the default section
246: using the name
247: .Dq asn1 .
248: The encoded data is passed through the ASN1 parser and printed out as
249: though it came from a file;
250: the contents can thus be examined and written to a file using the
251: .Fl out
252: option.
253: .It Fl i
1.34 jmc 254: Indent the output according to the
1.1 jsing 255: .Qq depth
256: of the structures.
257: .It Fl in Ar file
1.41 jmc 258: The input file to read from, or standard input if not specified.
1.34 jmc 259: .It Fl inform Cm der | pem | txt
1.1 jsing 260: The input format.
261: .It Fl length Ar number
1.34 jmc 262: Number of bytes to parse; the default is until end of file.
1.1 jsing 263: .It Fl noout
1.46 jmc 264: Do not output the parsed version of the input file.
1.1 jsing 265: .It Fl offset Ar number
1.34 jmc 266: Starting offset to begin parsing; the default is start of file.
1.1 jsing 267: .It Fl oid Ar file
268: A file containing additional object identifiers
269: .Pq OIDs .
270: If an OID
271: .Pq object identifier
272: is not part of
1.34 jmc 273: .Nm openssl Ns 's
1.1 jsing 274: internal table it will be represented in
275: numerical form
276: .Pq for example 1.2.3.4 .
1.34 jmc 277: .Pp
1.1 jsing 278: Each line consists of three columns:
279: the first column is the OID in numerical format and should be followed by
280: whitespace.
281: The second column is the
1.34 jmc 282: .Qq short name ,
1.1 jsing 283: which is a single word followed by whitespace.
284: The final column is the rest of the line and is the
285: .Qq long name .
286: .Nm asn1parse
287: displays the long name.
1.34 jmc 288: .It Fl out Ar file
289: The DER-encoded output file; the default is no encoded output
290: (useful when combined with
291: .Fl strparse ) .
292: .It Fl strparse Ar offset
293: Parse the content octets of the ASN.1 object starting at
294: .Ar offset .
295: This option can be used multiple times to
296: .Qq drill down
297: into a nested structure.
298: .El
1.1 jsing 299: .Sh CA
300: .nr nS 1
301: .Nm "openssl ca"
302: .Op Fl batch
303: .Op Fl cert Ar file
304: .Op Fl config Ar file
305: .Op Fl crl_CA_compromise Ar time
306: .Op Fl crl_compromise Ar time
307: .Op Fl crl_hold Ar instruction
308: .Op Fl crl_reason Ar reason
309: .Op Fl crldays Ar days
310: .Op Fl crlexts Ar section
311: .Op Fl crlhours Ar hours
312: .Op Fl days Ar arg
313: .Op Fl enddate Ar date
314: .Op Fl extensions Ar section
315: .Op Fl extfile Ar section
316: .Op Fl gencrl
317: .Op Fl in Ar file
318: .Op Fl infiles
319: .Op Fl key Ar keyfile
320: .Op Fl keyfile Ar arg
1.22 bcook 321: .Op Fl keyform Ar PEM
1.1 jsing 322: .Op Fl md Ar arg
323: .Op Fl msie_hack
324: .Op Fl name Ar section
325: .Op Fl noemailDN
326: .Op Fl notext
327: .Op Fl out Ar file
328: .Op Fl outdir Ar dir
329: .Op Fl passin Ar arg
330: .Op Fl policy Ar arg
331: .Op Fl preserveDN
332: .Op Fl revoke Ar file
333: .Op Fl spkac Ar file
334: .Op Fl ss_cert Ar file
335: .Op Fl startdate Ar date
336: .Op Fl status Ar serial
337: .Op Fl subj Ar arg
338: .Op Fl updatedb
339: .Op Fl verbose
340: .nr nS 0
341: .Pp
342: The
343: .Nm ca
1.35 jmc 344: command is a minimal certificate authority (CA) application.
1.1 jsing 345: It can be used to sign certificate requests in a variety of forms
1.35 jmc 346: and generate certificate revocation lists (CRLs).
1.1 jsing 347: It also maintains a text database of issued certificates and their status.
348: .Pp
1.35 jmc 349: The options relevant to CAs are as follows:
1.1 jsing 350: .Bl -tag -width "XXXX"
351: .It Fl batch
1.41 jmc 352: Batch mode.
1.1 jsing 353: In this mode no questions will be asked
354: and all certificates will be certified automatically.
355: .It Fl cert Ar file
356: The CA certificate file.
357: .It Fl config Ar file
358: Specifies the configuration file to use.
359: .It Fl days Ar arg
360: The number of days to certify the certificate for.
361: .It Fl enddate Ar date
1.41 jmc 362: Set the expiry date.
1.1 jsing 363: The format of the date is YYMMDDHHMMSSZ
364: .Pq the same as an ASN1 UTCTime structure .
365: .It Fl extensions Ar section
366: The section of the configuration file containing certificate extensions
367: to be added when a certificate is issued (defaults to
1.35 jmc 368: .Cm x509_extensions
1.1 jsing 369: unless the
370: .Fl extfile
371: option is used).
372: If no extension section is present, a V1 certificate is created.
373: If the extension section is present
374: .Pq even if it is empty ,
375: then a V3 certificate is created.
376: .It Fl extfile Ar file
377: An additional configuration
378: .Ar file
379: to read certificate extensions from
380: (using the default section unless the
381: .Fl extensions
382: option is also used).
383: .It Fl in Ar file
384: An input
385: .Ar file
386: containing a single certificate request to be signed by the CA.
387: .It Fl infiles
388: If present, this should be the last option; all subsequent arguments
389: are assumed to be the names of files containing certificate requests.
390: .It Fl key Ar keyfile
391: The password used to encrypt the private key.
1.35 jmc 392: Since on some systems the command line arguments are visible,
393: this option should be used with caution.
1.1 jsing 394: .It Fl keyfile Ar file
395: The private key to sign requests with.
1.22 bcook 396: .It Fl keyform Ar PEM
1.1 jsing 397: Private key file format.
398: .It Fl md Ar alg
399: The message digest to use.
400: Possible values include
401: .Ar md5
402: and
403: .Ar sha1 .
404: This option also applies to CRLs.
405: .It Fl msie_hack
406: This is a legacy option to make
407: .Nm ca
408: work with very old versions of the IE certificate enrollment control
409: .Qq certenr3 .
410: It used UniversalStrings for almost everything.
411: Since the old control has various security bugs,
412: its use is strongly discouraged.
413: The newer control
414: .Qq Xenroll
415: does not need this option.
416: .It Fl name Ar section
417: Specifies the configuration file
418: .Ar section
419: to use (overrides
420: .Cm default_ca
421: in the
422: .Cm ca
423: section).
424: .It Fl noemailDN
425: The DN of a certificate can contain the EMAIL field if present in the
1.30 mmcc 426: request DN, however it is good policy just having the email set into
1.1 jsing 427: the
1.35 jmc 428: .Cm altName
1.1 jsing 429: extension of the certificate.
430: When this option is set, the EMAIL field is removed from the certificate's
431: subject and set only in the, eventually present, extensions.
432: The
433: .Ar email_in_dn
434: keyword can be used in the configuration file to enable this behaviour.
435: .It Fl notext
436: Don't output the text form of a certificate to the output file.
437: .It Fl out Ar file
438: The output file to output certificates to.
439: The default is standard output.
440: The certificate details will also be printed out to this file.
441: .It Fl outdir Ar directory
442: The
443: .Ar directory
444: to output certificates to.
445: The certificate will be written to a file consisting of the
446: serial number in hex with
447: .Qq .pem
448: appended.
449: .It Fl passin Ar arg
450: The key password source.
451: .It Fl policy Ar arg
1.41 jmc 452: Define the CA
1.1 jsing 453: .Qq policy
454: to use.
1.35 jmc 455: The policy section in the configuration file
456: consists of a set of variables corresponding to certificate DN fields.
457: The values may be one of
458: .Qq match
459: (the value must match the same field in the CA certificate),
460: .Qq supplied
461: (the value must be present), or
462: .Qq optional
463: (the value may be present).
464: Any fields not mentioned in the policy section
465: are silently deleted, unless the
466: .Fl preserveDN
467: option is set,
468: but this can be regarded more of a quirk than intended behaviour.
1.1 jsing 469: .It Fl preserveDN
470: Normally, the DN order of a certificate is the same as the order of the
471: fields in the relevant policy section.
472: When this option is set, the order is the same as the request.
473: This is largely for compatibility with the older IE enrollment control
474: which would only accept certificates if their DNs matched the order of the
475: request.
476: This is not needed for Xenroll.
477: .It Fl spkac Ar file
478: A file containing a single Netscape signed public key and challenge,
479: and additional field values to be signed by the CA.
1.35 jmc 480: This will usually come from the
481: KEYGEN tag in an HTML form to create a new private key.
482: It is, however, possible to create SPKACs using the
483: .Nm spkac
484: utility.
485: .Pp
486: The file should contain the variable SPKAC set to the value of
487: the SPKAC and also the required DN components as name value pairs.
488: If it's necessary to include the same component twice,
489: then it can be preceded by a number and a
490: .Sq \&. .
1.1 jsing 491: .It Fl ss_cert Ar file
492: A single self-signed certificate to be signed by the CA.
493: .It Fl startdate Ar date
1.41 jmc 494: Set the start date.
1.1 jsing 495: The format of the date is YYMMDDHHMMSSZ
496: .Pq the same as an ASN1 UTCTime structure .
497: .It Fl status Ar serial
1.35 jmc 498: Show the status of the certificate with serial number
1.1 jsing 499: .Ar serial .
500: .It Fl updatedb
501: Update database for expired certificates.
502: .It Fl verbose
1.41 jmc 503: Print extra details about the operations being performed.
1.1 jsing 504: .El
1.35 jmc 505: .Pp
506: The options relevant to CRLs are as follows:
1.1 jsing 507: .Bl -tag -width "XXXX"
508: .It Fl crl_CA_compromise Ar time
509: This is the same as
510: .Fl crl_compromise ,
511: except the revocation reason is set to CACompromise.
512: .It Fl crl_compromise Ar time
1.41 jmc 513: Set the revocation reason to keyCompromise and the compromise time to
1.1 jsing 514: .Ar time .
515: .Ar time
516: should be in GeneralizedTime format, i.e. YYYYMMDDHHMMSSZ.
517: .It Fl crl_hold Ar instruction
1.41 jmc 518: Set the CRL revocation reason code to certificateHold and the hold
1.1 jsing 519: instruction to
520: .Ar instruction
521: which must be an OID.
522: Although any OID can be used, only holdInstructionNone
523: (the use of which is discouraged by RFC 2459), holdInstructionCallIssuer or
524: holdInstructionReject will normally be used.
525: .It Fl crl_reason Ar reason
526: Revocation reason, where
527: .Ar reason
528: is one of:
529: unspecified, keyCompromise, CACompromise, affiliationChanged, superseded,
530: cessationOfOperation, certificateHold or removeFromCRL.
531: The matching of
532: .Ar reason
533: is case insensitive.
534: Setting any revocation reason will make the CRL v2.
535: In practice, removeFromCRL is not particularly useful because it is only used
536: in delta CRLs which are not currently implemented.
537: .It Fl crldays Ar num
538: The number of days before the next CRL is due.
539: This is the days from now to place in the CRL
1.35 jmc 540: .Cm nextUpdate
1.1 jsing 541: field.
542: .It Fl crlexts Ar section
543: The
544: .Ar section
545: of the configuration file containing CRL extensions to include.
546: If no CRL extension section is present then a V1 CRL is created;
547: if the CRL extension section is present
548: .Pq even if it is empty
549: then a V2 CRL is created.
550: The CRL extensions specified are CRL extensions and
551: .Em not
552: CRL entry extensions.
553: It should be noted that some software
554: .Pq for example Netscape
555: can't handle V2 CRLs.
556: .It Fl crlhours Ar num
557: The number of hours before the next CRL is due.
558: .It Fl gencrl
1.41 jmc 559: Generate a CRL based on information in the index file.
1.1 jsing 560: .It Fl revoke Ar file
561: A
562: .Ar file
563: containing a certificate to revoke.
564: .It Fl subj Ar arg
565: Supersedes the subject name given in the request.
566: The
567: .Ar arg
568: must be formatted as
569: .Ar /type0=value0/type1=value1/type2=... ;
570: characters may be escaped by
571: .Sq \e
572: .Pq backslash ,
573: no spaces are skipped.
574: .El
575: .Pp
1.35 jmc 576: Many of the options can be set in the
577: .Cm ca
578: section of the configuration file
579: (or in the default section of the configuration file),
580: specified using
581: .Cm default_ca
582: or
583: .Fl name .
584: The options
585: .Cm preserve
586: and
587: .Cm msie_hack
588: are read directly from the
589: .Cm ca
590: section.
1.1 jsing 591: .Pp
592: Many of the configuration file options are identical to command line
593: options.
594: Where the option is present in the configuration file and the command line,
595: the command line value is used.
596: Where an option is described as mandatory, then it must be present in
597: the configuration file or the command line equivalent
598: .Pq if any
599: used.
600: .Bl -tag -width "XXXX"
1.35 jmc 601: .It Cm certificate
1.1 jsing 602: The same as
603: .Fl cert .
604: It gives the file containing the CA certificate.
605: Mandatory.
1.35 jmc 606: .It Cm copy_extensions
1.1 jsing 607: Determines how extensions in certificate requests should be handled.
608: If set to
1.35 jmc 609: .Cm none
1.1 jsing 610: or this option is not present, then extensions are
611: ignored and not copied to the certificate.
612: If set to
1.35 jmc 613: .Cm copy ,
1.1 jsing 614: then any extensions present in the request that are not already present
615: are copied to the certificate.
616: If set to
1.35 jmc 617: .Cm copyall ,
1.1 jsing 618: then all extensions in the request are copied to the certificate:
619: if the extension is already present in the certificate it is deleted first.
1.35 jmc 620: .Pp
621: The
622: .Cm copy_extensions
623: option should be used with caution.
624: If care is not taken, it can be a security risk.
625: For example, if a certificate request contains a
626: .Cm basicConstraints
627: extension with CA:TRUE and the
628: .Cm copy_extensions
629: value is set to
630: .Cm copyall
631: and the user does not spot
632: this when the certificate is displayed, then this will hand the requestor
633: a valid CA certificate.
634: .Pp
635: This situation can be avoided by setting
636: .Cm copy_extensions
637: to
638: .Cm copy
639: and including
640: .Cm basicConstraints
641: with CA:FALSE in the configuration file.
642: Then if the request contains a
643: .Cm basicConstraints
644: extension, it will be ignored.
1.1 jsing 645: .Pp
646: The main use of this option is to allow a certificate request to supply
647: values for certain extensions such as
1.35 jmc 648: .Cm subjectAltName .
649: .It Cm crl_extensions
1.1 jsing 650: The same as
651: .Fl crlexts .
1.35 jmc 652: .It Cm crlnumber
1.1 jsing 653: A text file containing the next CRL number to use in hex.
654: The CRL number will be inserted in the CRLs only if this file exists.
655: If this file is present, it must contain a valid CRL number.
1.35 jmc 656: .It Cm database
1.1 jsing 657: The text database file to use.
658: Mandatory.
659: This file must be present, though initially it will be empty.
1.35 jmc 660: .It Cm default_crl_hours , default_crl_days
1.1 jsing 661: The same as the
662: .Fl crlhours
663: and
664: .Fl crldays
665: options.
666: These will only be used if neither command line option is present.
667: At least one of these must be present to generate a CRL.
1.35 jmc 668: .It Cm default_days
1.1 jsing 669: The same as the
670: .Fl days
671: option.
672: The number of days to certify a certificate for.
1.35 jmc 673: .It Cm default_enddate
1.1 jsing 674: The same as the
675: .Fl enddate
676: option.
677: Either this option or
1.35 jmc 678: .Cm default_days
1.1 jsing 679: .Pq or the command line equivalents
680: must be present.
1.35 jmc 681: .It Cm default_md
1.1 jsing 682: The same as the
683: .Fl md
684: option.
685: The message digest to use.
686: Mandatory.
1.35 jmc 687: .It Cm default_startdate
1.1 jsing 688: The same as the
689: .Fl startdate
690: option.
691: The start date to certify a certificate for.
692: If not set, the current time is used.
1.35 jmc 693: .It Cm email_in_dn
1.1 jsing 694: The same as
695: .Fl noemailDN .
696: If the EMAIL field is to be removed from the DN of the certificate,
697: simply set this to
698: .Qq no .
699: If not present, the default is to allow for the EMAIL field in the
700: certificate's DN.
1.35 jmc 701: .It Cm msie_hack
1.1 jsing 702: The same as
703: .Fl msie_hack .
1.35 jmc 704: .It Cm name_opt , cert_opt
1.1 jsing 705: These options allow the format used to display the certificate details
706: when asking the user to confirm signing.
707: All the options supported by the
708: .Nm x509
709: utilities'
710: .Fl nameopt
711: and
712: .Fl certopt
713: switches can be used here, except that
1.35 jmc 714: .Cm no_signame
1.1 jsing 715: and
1.35 jmc 716: .Cm no_sigdump
1.1 jsing 717: are permanently set and cannot be disabled
718: (this is because the certificate signature cannot be displayed because
719: the certificate has not been signed at this point).
720: .Pp
721: For convenience, the value
1.35 jmc 722: .Cm ca_default
1.1 jsing 723: is accepted by both to produce a reasonable output.
724: .Pp
725: If neither option is present, the format used in earlier versions of
1.35 jmc 726: .Nm openssl
1.1 jsing 727: is used.
728: Use of the old format is
729: .Em strongly
730: discouraged because it only displays fields mentioned in the
1.35 jmc 731: .Cm policy
1.1 jsing 732: section,
733: mishandles multicharacter string types and does not display extensions.
1.35 jmc 734: .It Cm new_certs_dir
1.1 jsing 735: The same as the
736: .Fl outdir
737: command line option.
738: It specifies the directory where new certificates will be placed.
739: Mandatory.
1.35 jmc 740: .It Cm oid_file
1.1 jsing 741: This specifies a file containing additional object identifiers.
742: Each line of the file should consist of the numerical form of the
743: object identifier followed by whitespace, then the short name followed
744: by whitespace and finally the long name.
1.35 jmc 745: .It Cm oid_section
1.1 jsing 746: This specifies a section in the configuration file containing extra
747: object identifiers.
748: Each line should consist of the short name of the object identifier
749: followed by
750: .Sq =
751: and the numerical form.
752: The short and long names are the same when this option is used.
1.35 jmc 753: .It Cm policy
1.1 jsing 754: The same as
755: .Fl policy .
756: Mandatory.
1.35 jmc 757: .It Cm preserve
1.1 jsing 758: The same as
759: .Fl preserveDN .
1.35 jmc 760: .It Cm private_key
1.1 jsing 761: Same as the
762: .Fl keyfile
763: option.
764: The file containing the CA private key.
765: Mandatory.
1.35 jmc 766: .It Cm serial
1.1 jsing 767: A text file containing the next serial number to use in hex.
768: Mandatory.
769: This file must be present and contain a valid serial number.
1.35 jmc 770: .It Cm unique_subject
1.1 jsing 771: If the value
1.35 jmc 772: .Cm yes
1.1 jsing 773: is given, the valid certificate entries in the
774: database must have unique subjects.
775: If the value
1.35 jmc 776: .Cm no
1.1 jsing 777: is given,
778: several valid certificate entries may have the exact same subject.
779: The default value is
1.35 jmc 780: .Cm yes .
781: .It Cm x509_extensions
1.1 jsing 782: The same as
783: .Fl extensions .
784: .El
785: .Sh CIPHERS
786: .Nm openssl ciphers
787: .Op Fl hVv
1.18 jmc 788: .Op Fl tls1
1.1 jsing 789: .Op Ar cipherlist
790: .Pp
791: The
792: .Nm ciphers
793: command converts
1.36 jmc 794: .Nm openssl
1.1 jsing 795: cipher lists into ordered SSL cipher preference lists.
1.41 jmc 796: It can be used as a way to determine the appropriate cipher list.
1.1 jsing 797: .Pp
798: The options are as follows:
799: .Bl -tag -width Ds
800: .It Fl h , \&?
801: Print a brief usage message.
802: .It Fl tls1
803: Only include TLS v1 ciphers.
804: .It Fl V
1.36 jmc 805: Verbose.
806: List ciphers with a complete description of protocol version,
807: key exchange, authentication, encryption and mac algorithms,
808: any key size restrictions,
809: and cipher suite codes (hex format).
810: .It Fl v
1.1 jsing 811: Like
1.36 jmc 812: .Fl V ,
813: but without cipher suite codes.
1.1 jsing 814: .It Ar cipherlist
815: A cipher list to convert to a cipher preference list.
816: If it is not included, the default cipher list will be used.
1.36 jmc 817: .Pp
818: The cipher list consists of one or more cipher strings
1.1 jsing 819: separated by colons.
820: Commas or spaces are also acceptable separators, but colons are normally used.
821: .Pp
1.36 jmc 822: The actual cipher string can take several different forms:
1.1 jsing 823: .Pp
1.36 jmc 824: It can consist of a single cipher suite, such as RC4-SHA.
1.1 jsing 825: .Pp
826: It can represent a list of cipher suites containing a certain algorithm,
827: or cipher suites of a certain type.
1.36 jmc 828: For example SHA1 represents all cipher suites using the digest algorithm SHA1.
829: .Pp
830: Lists of cipher suites can be combined in a single cipher string using the
1.1 jsing 831: .Sq +
1.36 jmc 832: character
833: (logical AND operation).
834: For example, SHA1+DES represents all cipher suites
835: containing the SHA1 and DES algorithms.
1.1 jsing 836: .Pp
837: Each cipher string can be optionally preceded by the characters
838: .Sq \&! ,
839: .Sq - ,
840: or
841: .Sq + .
842: If
843: .Sq !\&
844: is used, then the ciphers are permanently deleted from the list.
845: The ciphers deleted can never reappear in the list even if they are
846: explicitly stated.
847: If
848: .Sq -
849: is used, then the ciphers are deleted from the list, but some or
850: all of the ciphers can be added again by later options.
851: If
852: .Sq +
853: is used, then the ciphers are moved to the end of the list.
854: This option doesn't add any new ciphers, it just moves matching existing ones.
855: .Pp
856: If none of these characters is present, the string is just interpreted
857: as a list of ciphers to be appended to the current preference list.
858: If the list includes any ciphers already present, they will be ignored;
859: that is, they will not be moved to the end of the list.
860: .Pp
861: Additionally, the cipher string
1.36 jmc 862: .Cm @STRENGTH
1.1 jsing 863: can be used at any point to sort the current cipher list in order of
864: encryption algorithm key length.
1.36 jmc 865: .El
866: .Pp
1.1 jsing 867: The following is a list of all permitted cipher strings and their meanings.
868: .Bl -tag -width "XXXX"
1.36 jmc 869: .It Cm DEFAULT
1.1 jsing 870: The default cipher list.
871: This is determined at compile time and is currently
1.36 jmc 872: .Cm ALL:!aNULL:!eNULL:!SSLv2 .
873: This must be the first cipher string specified.
874: .It Cm COMPLEMENTOFDEFAULT
1.1 jsing 875: The ciphers included in
1.36 jmc 876: .Cm ALL ,
1.1 jsing 877: but not enabled by default.
878: Currently this is
1.36 jmc 879: .Cm ADH .
1.1 jsing 880: Note that this rule does not cover
1.36 jmc 881: .Cm eNULL ,
1.1 jsing 882: which is not included by
1.36 jmc 883: .Cm ALL
1.1 jsing 884: (use
1.36 jmc 885: .Cm COMPLEMENTOFALL
1.1 jsing 886: if necessary).
1.36 jmc 887: .It Cm ALL
1.1 jsing 888: All cipher suites except the
1.36 jmc 889: .Cm eNULL
890: ciphers, which must be explicitly enabled.
891: .It Cm COMPLEMENTOFALL
1.1 jsing 892: The cipher suites not enabled by
1.36 jmc 893: .Cm ALL ,
1.1 jsing 894: currently being
1.36 jmc 895: .Cm eNULL .
896: .It Cm HIGH
1.1 jsing 897: .Qq High
898: encryption cipher suites.
899: This currently means those with key lengths larger than 128 bits.
1.36 jmc 900: .It Cm MEDIUM
1.1 jsing 901: .Qq Medium
902: encryption cipher suites, currently those using 128-bit encryption.
1.36 jmc 903: .It Cm LOW
1.1 jsing 904: .Qq Low
905: encryption cipher suites, currently those using 64- or 56-bit encryption
1.9 lteo 906: algorithms.
1.36 jmc 907: .It Cm eNULL , NULL
1.1 jsing 908: The
909: .Qq NULL
910: ciphers; that is, those offering no encryption.
911: Because these offer no encryption at all and are a security risk,
912: they are disabled unless explicitly included.
1.36 jmc 913: .It Cm aNULL
1.1 jsing 914: The cipher suites offering no authentication.
915: This is currently the anonymous DH algorithms.
916: These cipher suites are vulnerable to a
917: .Qq man in the middle
918: attack, so their use is normally discouraged.
1.36 jmc 919: .It Cm kRSA , RSA
1.1 jsing 920: Cipher suites using RSA key exchange.
1.36 jmc 921: .It Cm kEDH
1.1 jsing 922: Cipher suites using ephemeral DH key agreement.
1.36 jmc 923: .It Cm aRSA
1.1 jsing 924: Cipher suites using RSA authentication, i.e. the certificates carry RSA keys.
1.36 jmc 925: .It Cm aDSS , DSS
1.1 jsing 926: Cipher suites using DSS authentication, i.e. the certificates carry DSS keys.
1.36 jmc 927: .It Cm TLSv1
1.18 jmc 928: TLS v1.0 cipher suites.
1.36 jmc 929: .It Cm DH
1.1 jsing 930: Cipher suites using DH, including anonymous DH.
1.36 jmc 931: .It Cm ADH
1.1 jsing 932: Anonymous DH cipher suites.
1.36 jmc 933: .It Cm AES
1.1 jsing 934: Cipher suites using AES.
1.36 jmc 935: .It Cm 3DES
1.1 jsing 936: Cipher suites using triple DES.
1.36 jmc 937: .It Cm DES
1.1 jsing 938: Cipher suites using DES
939: .Pq not triple DES .
1.36 jmc 940: .It Cm RC4
1.1 jsing 941: Cipher suites using RC4.
1.36 jmc 942: .It Cm CAMELLIA
1.9 lteo 943: Cipher suites using Camellia.
1.36 jmc 944: .It Cm CHACHA20
1.9 lteo 945: Cipher suites using ChaCha20.
1.36 jmc 946: .It Cm IDEA
1.9 lteo 947: Cipher suites using IDEA.
1.36 jmc 948: .It Cm MD5
1.1 jsing 949: Cipher suites using MD5.
1.36 jmc 950: .It Cm SHA1 , SHA
1.1 jsing 951: Cipher suites using SHA1.
952: .El
953: .Sh CRL
954: .nr nS 1
955: .Nm "openssl crl"
956: .Op Fl CAfile Ar file
957: .Op Fl CApath Ar dir
958: .Op Fl fingerprint
959: .Op Fl hash
960: .Op Fl in Ar file
1.38 jmc 961: .Op Fl inform Cm der | pem
1.1 jsing 962: .Op Fl issuer
963: .Op Fl lastupdate
964: .Op Fl nextupdate
965: .Op Fl noout
966: .Op Fl out Ar file
1.38 jmc 967: .Op Fl outform Cm der | pem
1.1 jsing 968: .Op Fl text
969: .nr nS 0
970: .Pp
971: The
972: .Nm crl
973: command processes CRL files in DER or PEM format.
1.37 jmc 974: .Pp
1.1 jsing 975: The options are as follows:
976: .Bl -tag -width Ds
977: .It Fl CAfile Ar file
978: Verify the signature on a CRL by looking up the issuing certificate in
979: .Ar file .
980: .It Fl CApath Ar directory
981: Verify the signature on a CRL by looking up the issuing certificate in
982: .Ar dir .
983: This directory must be a standard certificate directory,
984: i.e. a hash of each subject name (using
985: .Cm x509 Fl hash )
986: should be linked to each certificate.
987: .It Fl fingerprint
988: Print the CRL fingerprint.
989: .It Fl hash
990: Output a hash of the issuer name.
991: This can be used to look up CRLs in a directory by issuer name.
992: .It Fl in Ar file
1.37 jmc 993: The input file to read from, or standard input if not specified.
1.38 jmc 994: .It Fl inform Cm der | pem
1.37 jmc 995: The input format.
1.1 jsing 996: .It Fl issuer
997: Output the issuer name.
998: .It Fl lastupdate
999: Output the
1.37 jmc 1000: .Cm lastUpdate
1.1 jsing 1001: field.
1002: .It Fl nextupdate
1003: Output the
1.37 jmc 1004: .Cm nextUpdate
1.1 jsing 1005: field.
1006: .It Fl noout
1.46 jmc 1007: Do not output the encoded version of the CRL.
1.1 jsing 1008: .It Fl out Ar file
1.37 jmc 1009: The output file to write to, or standard output if not specified.
1.38 jmc 1010: .It Fl outform Cm der | pem
1.37 jmc 1011: The output format.
1.1 jsing 1012: .It Fl text
1.64 jmc 1013: Print the CRL in plain text.
1.1 jsing 1014: .El
1015: .Sh CRL2PKCS7
1016: .nr nS 1
1017: .Nm "openssl crl2pkcs7"
1018: .Op Fl certfile Ar file
1019: .Op Fl in Ar file
1.40 jmc 1020: .Op Fl inform Cm der | pem
1.1 jsing 1021: .Op Fl nocrl
1022: .Op Fl out Ar file
1.40 jmc 1023: .Op Fl outform Cm der | pem
1.1 jsing 1024: .nr nS 0
1025: .Pp
1026: The
1027: .Nm crl2pkcs7
1028: command takes an optional CRL and one or more
1029: certificates and converts them into a PKCS#7 degenerate
1030: .Qq certificates only
1031: structure.
1032: .Pp
1033: The options are as follows:
1034: .Bl -tag -width Ds
1035: .It Fl certfile Ar file
1.40 jmc 1036: Add the certificates in PEM
1.1 jsing 1037: .Ar file
1.40 jmc 1038: to the PKCS#7 structure.
1039: This option can be used more than once
1040: to read certificates from multiple files.
1.1 jsing 1041: .It Fl in Ar file
1.40 jmc 1042: Read the CRL from
1043: .Ar file ,
1044: or standard input if not specified.
1045: .It Fl inform Cm der | pem
1.64 jmc 1046: The input format.
1.1 jsing 1047: .It Fl nocrl
1048: Normally, a CRL is included in the output file.
1049: With this option, no CRL is
1050: included in the output file and a CRL is not read from the input file.
1051: .It Fl out Ar file
1.40 jmc 1052: Write the PKCS#7 structure to
1053: .Ar file ,
1054: or standard output if not specified.
1055: .It Fl outform Cm der | pem
1.64 jmc 1056: The output format.
1.1 jsing 1057: .El
1058: .Sh DGST
1059: .nr nS 1
1060: .Nm "openssl dgst"
1.43 jmc 1061: .Op Fl cd
1.1 jsing 1062: .Op Fl binary
1.43 jmc 1063: .Op Fl Ar digest
1.1 jsing 1064: .Op Fl hex
1065: .Op Fl hmac Ar key
1.43 jmc 1066: .Op Fl keyform Cm pem
1.1 jsing 1067: .Op Fl mac Ar algorithm
1068: .Op Fl macopt Ar nm : Ns Ar v
1069: .Op Fl out Ar file
1070: .Op Fl passin Ar arg
1071: .Op Fl prverify Ar file
1072: .Op Fl sign Ar file
1073: .Op Fl signature Ar file
1074: .Op Fl sigopt Ar nm : Ns Ar v
1075: .Op Fl verify Ar file
1076: .Op Ar
1077: .nr nS 0
1078: .Pp
1079: The digest functions output the message digest of a supplied
1080: .Ar file
1081: or
1082: .Ar files
1083: in hexadecimal form.
1084: They can also be used for digital signing and verification.
1085: .Pp
1086: The options are as follows:
1087: .Bl -tag -width Ds
1088: .It Fl binary
1089: Output the digest or signature in binary form.
1090: .It Fl c
1.48 jmc 1091: Print the digest in two-digit groups separated by colons.
1.1 jsing 1092: .It Fl d
1.48 jmc 1093: Print BIO debugging information.
1.43 jmc 1094: .It Fl Ar digest
1095: Use the specified message
1096: .Ar digest .
1097: The default is MD5.
1098: The available digests can be displayed using
1099: .Nm openssl
1100: .Cm list-message-digest-commands .
1101: The following are equivalent:
1102: .Nm openssl dgst
1103: .Fl md5
1104: and
1105: .Nm openssl
1106: .Cm md5 .
1.1 jsing 1107: .It Fl hex
1108: Digest is to be output as a hex dump.
1109: This is the default case for a
1110: .Qq normal
1111: digest as opposed to a digital signature.
1112: .It Fl hmac Ar key
1113: Create a hashed MAC using
1114: .Ar key .
1.43 jmc 1115: .It Fl keyform Cm pem
1.1 jsing 1116: Specifies the key format to sign the digest with.
1117: .It Fl mac Ar algorithm
1118: Create a keyed Message Authentication Code (MAC).
1119: The most popular MAC algorithm is HMAC (hash-based MAC),
1120: but there are other MAC algorithms which are not based on hash.
1121: MAC keys and other options should be set via the
1122: .Fl macopt
1123: parameter.
1124: .It Fl macopt Ar nm : Ns Ar v
1125: Passes options to the MAC algorithm, specified by
1126: .Fl mac .
1127: The following options are supported by HMAC:
1128: .Bl -tag -width Ds
1.43 jmc 1129: .It Cm key : Ns Ar string
1.1 jsing 1130: Specifies the MAC key as an alphanumeric string
1131: (use if the key contain printable characters only).
1132: String length must conform to any restrictions of the MAC algorithm.
1.43 jmc 1133: .It Cm hexkey : Ns Ar string
1.1 jsing 1134: Specifies the MAC key in hexadecimal form (two hex digits per byte).
1135: Key length must conform to any restrictions of the MAC algorithm.
1136: .El
1137: .It Fl out Ar file
1.43 jmc 1138: The output file to write to,
1139: or standard output if not specified.
1.1 jsing 1140: .It Fl passin Ar arg
1141: The key password source.
1142: .It Fl prverify Ar file
1143: Verify the signature using the private key in
1144: .Ar file .
1145: The output is either
1146: .Qq Verification OK
1147: or
1148: .Qq Verification Failure .
1149: .It Fl sign Ar file
1150: Digitally sign the digest using the private key in
1151: .Ar file .
1152: .It Fl signature Ar file
1153: The actual signature to verify.
1154: .It Fl sigopt Ar nm : Ns Ar v
1155: Pass options to the signature algorithm during sign or verify operations.
1156: The names and values of these options are algorithm-specific.
1157: .It Fl verify Ar file
1158: Verify the signature using the public key in
1159: .Ar file .
1160: The output is either
1161: .Qq Verification OK
1162: or
1163: .Qq Verification Failure .
1164: .It Ar
1165: File or files to digest.
1166: If no files are specified then standard input is used.
1167: .El
1168: .Sh DHPARAM
1169: .nr nS 1
1170: .Nm "openssl dhparam"
1171: .Op Fl 2 | 5
1172: .Op Fl C
1173: .Op Fl check
1174: .Op Fl dsaparam
1175: .Op Fl in Ar file
1.44 jmc 1176: .Op Fl inform Cm der | pem
1.1 jsing 1177: .Op Fl noout
1178: .Op Fl out Ar file
1.44 jmc 1179: .Op Fl outform Cm der | pem
1.1 jsing 1180: .Op Fl text
1181: .Op Ar numbits
1182: .nr nS 0
1183: .Pp
1184: The
1185: .Nm dhparam
1186: command is used to manipulate DH parameter files.
1.44 jmc 1187: Only the older PKCS#3 DH is supported,
1188: not the newer X9.42 DH.
1.1 jsing 1189: .Pp
1190: The options are as follows:
1191: .Bl -tag -width Ds
1192: .It Fl 2 , 5
1.44 jmc 1193: The generator to use;
1.1 jsing 1194: 2 is the default.
1195: If present, the input file is ignored and parameters are generated instead.
1196: .It Fl C
1.44 jmc 1197: Convert the parameters into C code.
1.1 jsing 1198: The parameters can then be loaded by calling the
1.44 jmc 1199: .No get_dh Ns Ar numbits
1.1 jsing 1200: function.
1201: .It Fl check
1202: Check the DH parameters.
1203: .It Fl dsaparam
1.44 jmc 1204: Read or create DSA parameters,
1205: converted to DH format on output.
1.1 jsing 1206: Otherwise,
1207: .Qq strong
1208: primes
1209: .Pq such that (p-1)/2 is also prime
1210: will be used for DH parameter generation.
1211: .Pp
1212: DH parameter generation with the
1213: .Fl dsaparam
1214: option is much faster,
1215: and the recommended exponent length is shorter,
1216: which makes DH key exchange more efficient.
1217: Beware that with such DSA-style DH parameters,
1218: a fresh DH key should be created for each use to
1219: avoid small-subgroup attacks that may be possible otherwise.
1220: .It Fl in Ar file
1.44 jmc 1221: The input file to read from,
1222: or standard input if not specified.
1223: .It Fl inform Cm der | pem
1224: The input format.
1.1 jsing 1225: .It Fl noout
1.46 jmc 1226: Do not output the encoded version of the parameters.
1.44 jmc 1227: .It Fl out Ar file
1228: The output file to write to,
1229: or standard output if not specified.
1230: .It Fl outform Cm der | pem
1231: The output format.
1232: .It Fl text
1.64 jmc 1233: Print the DH parameters in plain text.
1.1 jsing 1234: .It Ar numbits
1.44 jmc 1235: Generate a parameter set of size
1.1 jsing 1236: .Ar numbits .
1237: It must be the last option.
1.16 sthen 1238: If not present, a value of 2048 is used.
1.1 jsing 1239: If this value is present, the input file is ignored and
1240: parameters are generated instead.
1241: .El
1242: .Sh DSA
1243: .nr nS 1
1244: .Nm "openssl dsa"
1245: .Oo
1246: .Fl aes128 | aes192 | aes256 |
1247: .Fl des | des3
1248: .Oc
1249: .Op Fl in Ar file
1.45 jmc 1250: .Op Fl inform Cm der | pem
1.1 jsing 1251: .Op Fl modulus
1252: .Op Fl noout
1253: .Op Fl out Ar file
1.45 jmc 1254: .Op Fl outform Cm der | pem
1.1 jsing 1255: .Op Fl passin Ar arg
1256: .Op Fl passout Ar arg
1257: .Op Fl pubin
1258: .Op Fl pubout
1259: .Op Fl text
1260: .nr nS 0
1261: .Pp
1262: The
1263: .Nm dsa
1264: command processes DSA keys.
1265: They can be converted between various forms and their components printed out.
1266: .Pp
1267: .Sy Note :
1268: This command uses the traditional
1269: .Nm SSLeay
1270: compatible format for private key encryption:
1271: newer applications should use the more secure PKCS#8 format using the
1272: .Nm pkcs8
1273: command.
1274: .Pp
1275: The options are as follows:
1276: .Bl -tag -width Ds
1277: .It Xo
1278: .Fl aes128 | aes192 | aes256 |
1279: .Fl des | des3
1280: .Xc
1.45 jmc 1281: Encrypt the private key with the AES, DES, or the triple DES
1.1 jsing 1282: ciphers, respectively, before outputting it.
1283: A pass phrase is prompted for.
1.45 jmc 1284: If none of these options are specified, the key is written in plain text.
1.1 jsing 1285: This means that using the
1286: .Nm dsa
1.45 jmc 1287: utility to read an encrypted key with no encryption option can be used to
1.1 jsing 1288: remove the pass phrase from a key,
1.45 jmc 1289: or by setting the encryption options it can be used to add or change
1.1 jsing 1290: the pass phrase.
1291: These options can only be used with PEM format output files.
1292: .It Fl in Ar file
1.45 jmc 1293: The input file to read from,
1294: or standard input if not specified.
1.1 jsing 1295: If the key is encrypted, a pass phrase will be prompted for.
1.45 jmc 1296: .It Fl inform Cm der | pem
1297: The input format.
1.1 jsing 1298: .It Fl modulus
1.45 jmc 1299: Print the value of the public key component of the key.
1.1 jsing 1300: .It Fl noout
1.46 jmc 1301: Do not output the encoded version of the key.
1.1 jsing 1302: .It Fl out Ar file
1.45 jmc 1303: The output file to write to,
1304: or standard output if not specified.
1.1 jsing 1305: If any encryption options are set then a pass phrase will be
1306: prompted for.
1.45 jmc 1307: .It Fl outform Cm der | pem
1308: The output format.
1.1 jsing 1309: .It Fl passin Ar arg
1310: The key password source.
1311: .It Fl passout Ar arg
1312: The output file password source.
1313: .It Fl pubin
1.60 jmc 1314: Read in a public key, not a private key.
1.1 jsing 1315: .It Fl pubout
1.60 jmc 1316: Output a public key, not a private key.
1317: Automatically set if the input is a public key.
1.1 jsing 1318: .It Fl text
1.64 jmc 1319: Print the public/private key in plain text.
1.1 jsing 1320: .El
1321: .Sh DSAPARAM
1322: .nr nS 1
1323: .Nm "openssl dsaparam"
1324: .Op Fl C
1325: .Op Fl genkey
1326: .Op Fl in Ar file
1.46 jmc 1327: .Op Fl inform Cm der | pem
1.1 jsing 1328: .Op Fl noout
1329: .Op Fl out Ar file
1.46 jmc 1330: .Op Fl outform Cm der | pem
1.1 jsing 1331: .Op Fl text
1332: .Op Ar numbits
1333: .nr nS 0
1334: .Pp
1335: The
1336: .Nm dsaparam
1337: command is used to manipulate or generate DSA parameter files.
1338: .Pp
1339: The options are as follows:
1340: .Bl -tag -width Ds
1341: .It Fl C
1.46 jmc 1342: Convert the parameters into C code.
1.1 jsing 1343: The parameters can then be loaded by calling the
1.46 jmc 1344: .No get_dsa Ns Ar XXX
1.1 jsing 1345: function.
1346: .It Fl genkey
1.46 jmc 1347: Generate a DSA key either using the specified or generated
1.1 jsing 1348: parameters.
1349: .It Fl in Ar file
1.46 jmc 1350: The input file to read from,
1351: or standard input if not specified.
1.1 jsing 1352: If the
1353: .Ar numbits
1.46 jmc 1354: parameter is included, then this option is ignored.
1355: .It Fl inform Cm der | pem
1356: The input format.
1.1 jsing 1357: .It Fl noout
1.46 jmc 1358: Do not output the encoded version of the parameters.
1359: .It Fl out Ar file
1360: The output file to write to,
1361: or standard output if not specified.
1362: .It Fl outform Cm der | pem
1363: The output format.
1364: .It Fl text
1.64 jmc 1365: Print the DSA parameters in plain text.
1.1 jsing 1366: .It Ar numbits
1.46 jmc 1367: Generate a parameter set of size
1.1 jsing 1368: .Ar numbits .
1.46 jmc 1369: If this option is included, the input file is ignored.
1.1 jsing 1370: .El
1371: .Sh EC
1372: .nr nS 1
1373: .Nm "openssl ec"
1374: .Op Fl conv_form Ar arg
1375: .Op Fl des
1376: .Op Fl des3
1377: .Op Fl in Ar file
1.47 jmc 1378: .Op Fl inform Cm der | pem
1.1 jsing 1379: .Op Fl noout
1380: .Op Fl out Ar file
1.47 jmc 1381: .Op Fl outform Cm der | pem
1.1 jsing 1382: .Op Fl param_enc Ar arg
1383: .Op Fl param_out
1384: .Op Fl passin Ar arg
1385: .Op Fl passout Ar arg
1386: .Op Fl pubin
1387: .Op Fl pubout
1388: .Op Fl text
1389: .nr nS 0
1390: .Pp
1391: The
1392: .Nm ec
1393: command processes EC keys.
1394: They can be converted between various
1395: forms and their components printed out.
1.47 jmc 1396: .Nm openssl
1.1 jsing 1397: uses the private key format specified in
1398: .Dq SEC 1: Elliptic Curve Cryptography
1399: .Pq Lk http://www.secg.org/ .
1400: To convert an
1401: EC private key into the PKCS#8 private key format use the
1402: .Nm pkcs8
1403: command.
1404: .Pp
1405: The options are as follows:
1406: .Bl -tag -width Ds
1407: .It Fl conv_form Ar arg
1.47 jmc 1408: Specify how the points on the elliptic curve are converted
1.1 jsing 1409: into octet strings.
1410: Possible values are:
1411: .Cm compressed
1.47 jmc 1412: (the default),
1.1 jsing 1413: .Cm uncompressed ,
1414: and
1415: .Cm hybrid .
1416: For more information regarding
1.47 jmc 1417: the point conversion forms see the X9.62 standard.
1.1 jsing 1418: Note:
1419: Due to patent issues the
1420: .Cm compressed
1421: option is disabled by default for binary curves
1422: and can be enabled by defining the preprocessor macro
1.47 jmc 1423: .Dv OPENSSL_EC_BIN_PT_COMP
1.1 jsing 1424: at compile time.
1425: .It Fl des | des3
1.47 jmc 1426: Encrypt the private key with DES, triple DES, or
1.1 jsing 1427: any other cipher supported by
1.47 jmc 1428: .Nm openssl .
1.1 jsing 1429: A pass phrase is prompted for.
1430: If none of these options is specified the key is written in plain text.
1431: This means that using the
1432: .Nm ec
1433: utility to read in an encrypted key with no
1434: encryption option can be used to remove the pass phrase from a key,
1435: or by setting the encryption options
1436: it can be use to add or change the pass phrase.
1437: These options can only be used with PEM format output files.
1438: .It Fl in Ar file
1.47 jmc 1439: The input file to read a key from,
1440: or standard input if not specified.
1.1 jsing 1441: If the key is encrypted a pass phrase will be prompted for.
1.47 jmc 1442: .It Fl inform Cm der | pem
1443: The input format.
1.1 jsing 1444: .It Fl noout
1.47 jmc 1445: Do not output the encoded version of the key.
1.1 jsing 1446: .It Fl out Ar file
1.47 jmc 1447: The output filename to write to,
1448: or standard output if not specified.
1.1 jsing 1449: If any encryption options are set then a pass phrase will be prompted for.
1.47 jmc 1450: .It Fl outform Cm der | pem
1451: The output format.
1.1 jsing 1452: .It Fl param_enc Ar arg
1.47 jmc 1453: Specify how the elliptic curve parameters are encoded.
1.1 jsing 1454: Possible value are:
1455: .Cm named_curve ,
1456: i.e. the EC parameters are specified by an OID; or
1457: .Cm explicit ,
1458: where the EC parameters are explicitly given
1459: (see RFC 3279 for the definition of the EC parameter structures).
1460: The default value is
1461: .Cm named_curve .
1462: Note: the
1463: .Cm implicitlyCA
1464: alternative,
1465: as specified in RFC 3279,
1.47 jmc 1466: is currently not implemented.
1.1 jsing 1467: .It Fl passin Ar arg
1468: The key password source.
1469: .It Fl passout Ar arg
1470: The output file password source.
1471: .It Fl pubin
1.60 jmc 1472: Read in a public key, not a private key.
1.1 jsing 1473: .It Fl pubout
1.60 jmc 1474: Output a public key, not a private key.
1475: Automatically set if the input is a public key.
1.1 jsing 1476: .It Fl text
1.64 jmc 1477: Print the public/private key in plain text.
1.1 jsing 1478: .El
1479: .Sh ECPARAM
1480: .nr nS 1
1481: .Nm "openssl ecparam"
1482: .Op Fl C
1483: .Op Fl check
1484: .Op Fl conv_form Ar arg
1485: .Op Fl genkey
1486: .Op Fl in Ar file
1.48 jmc 1487: .Op Fl inform Cm der | pem
1.1 jsing 1488: .Op Fl list_curves
1489: .Op Fl name Ar arg
1490: .Op Fl no_seed
1491: .Op Fl noout
1492: .Op Fl out Ar file
1.48 jmc 1493: .Op Fl outform Cm der | pem
1.1 jsing 1494: .Op Fl param_enc Ar arg
1495: .Op Fl text
1496: .nr nS 0
1497: .Pp
1.48 jmc 1498: The
1499: .Nm ecparam
1500: command is used to manipulate or generate EC parameter files.
1501: .Nm openssl
1502: is not able to generate new groups so
1503: .Nm ecparam
1504: can only create EC parameters from known (named) curves.
1505: .Pp
1.1 jsing 1506: The options are as follows:
1507: .Bl -tag -width Ds
1508: .It Fl C
1509: Convert the EC parameters into C code.
1510: The parameters can then be loaded by calling the
1.48 jmc 1511: .No get_ec_group_ Ns Ar XXX
1.1 jsing 1512: function.
1513: .It Fl check
1514: Validate the elliptic curve parameters.
1515: .It Fl conv_form Ar arg
1516: Specify how the points on the elliptic curve are converted
1517: into octet strings.
1518: Possible values are:
1519: .Cm compressed
1.48 jmc 1520: (the default),
1.1 jsing 1521: .Cm uncompressed ,
1522: and
1523: .Cm hybrid .
1524: For more information regarding
1.48 jmc 1525: the point conversion forms see the X9.62 standard.
1.1 jsing 1526: Note:
1527: Due to patent issues the
1528: .Cm compressed
1529: option is disabled by default for binary curves
1530: and can be enabled by defining the preprocessor macro
1.48 jmc 1531: .Dv OPENSSL_EC_BIN_PT_COMP
1.1 jsing 1532: at compile time.
1533: .It Fl genkey
1534: Generate an EC private key using the specified parameters.
1535: .It Fl in Ar file
1.48 jmc 1536: The input file to read from,
1537: or standard input if not specified.
1538: .It Fl inform Cm der | pem
1539: The input format.
1.1 jsing 1540: .It Fl list_curves
1.48 jmc 1541: Print a list of all
1.1 jsing 1542: currently implemented EC parameter names and exit.
1543: .It Fl name Ar arg
1.48 jmc 1544: Use the EC parameters with the specified "short" name.
1.1 jsing 1545: .It Fl no_seed
1.48 jmc 1546: Do not include the seed for the parameter generation
1547: in the ECParameters structure (see RFC 3279).
1.1 jsing 1548: .It Fl noout
1.48 jmc 1549: Do not output the encoded version of the parameters.
1.1 jsing 1550: .It Fl out Ar file
1.48 jmc 1551: The output file to write to,
1552: or standard output if not specified.
1553: .It Fl outform Cm der | pem
1554: The output format.
1.1 jsing 1555: .It Fl param_enc Ar arg
1.48 jmc 1556: Specify how the elliptic curve parameters are encoded.
1.1 jsing 1557: Possible value are:
1558: .Cm named_curve ,
1559: i.e. the EC parameters are specified by an OID, or
1560: .Cm explicit ,
1561: where the EC parameters are explicitly given
1562: (see RFC 3279 for the definition of the EC parameter structures).
1563: The default value is
1564: .Cm named_curve .
1565: Note: the
1566: .Cm implicitlyCA
1567: alternative, as specified in RFC 3279,
1.48 jmc 1568: is currently not implemented.
1.1 jsing 1569: .It Fl text
1.64 jmc 1570: Print the EC parameters in plain text.
1.1 jsing 1571: .El
1572: .Sh ENC
1573: .nr nS 1
1574: .Nm "openssl enc"
1575: .Fl ciphername
1576: .Op Fl AadePp
1577: .Op Fl base64
1578: .Op Fl bufsize Ar number
1579: .Op Fl debug
1580: .Op Fl in Ar file
1581: .Op Fl iv Ar IV
1582: .Op Fl K Ar key
1583: .Op Fl k Ar password
1584: .Op Fl kfile Ar file
1585: .Op Fl md Ar digest
1586: .Op Fl none
1587: .Op Fl nopad
1588: .Op Fl nosalt
1589: .Op Fl out Ar file
1590: .Op Fl pass Ar arg
1591: .Op Fl S Ar salt
1592: .Op Fl salt
1593: .nr nS 0
1594: .Pp
1595: The symmetric cipher commands allow data to be encrypted or decrypted
1596: using various block and stream ciphers using keys based on passwords
1597: or explicitly provided.
1598: Base64 encoding or decoding can also be performed either by itself
1599: or in addition to the encryption or decryption.
1.49 jmc 1600: The program can be called either as
1601: .Nm openssl Ar ciphername
1602: or
1603: .Nm openssl enc - Ns Ar ciphername .
1604: .Pp
1605: Some of the ciphers do not have large keys and others have security
1606: implications if not used correctly.
1607: All the block ciphers normally use PKCS#5 padding,
1608: also known as standard block padding.
1609: If padding is disabled, the input data must be a multiple of the cipher
1610: block length.
1.1 jsing 1611: .Pp
1612: The options are as follows:
1613: .Bl -tag -width Ds
1614: .It Fl A
1615: If the
1616: .Fl a
1617: option is set, then base64 process the data on one line.
1618: .It Fl a , base64
1619: Base64 process the data.
1620: This means that if encryption is taking place, the data is base64-encoded
1621: after encryption.
1.49 jmc 1622: If decryption is set, the input data is base64-decoded before
1.1 jsing 1623: being decrypted.
1624: .It Fl bufsize Ar number
1625: Set the buffer size for I/O.
1626: .It Fl d
1627: Decrypt the input data.
1628: .It Fl debug
1629: Debug the BIOs used for I/O.
1630: .It Fl e
1.49 jmc 1631: Encrypt the input data.
1632: This is the default.
1.1 jsing 1633: .It Fl in Ar file
1.49 jmc 1634: The input file to read from,
1.57 jmc 1635: or standard input if not specified.
1.1 jsing 1636: .It Fl iv Ar IV
1637: The actual
1638: .Ar IV
1639: .Pq initialisation vector
1640: to use:
1641: this must be represented as a string comprised only of hex digits.
1642: When only the
1643: .Ar key
1644: is specified using the
1645: .Fl K
1.49 jmc 1646: option,
1647: the IV must explicitly be defined.
1.1 jsing 1648: When a password is being specified using one of the other options,
1.49 jmc 1649: the IV is generated from this password.
1.1 jsing 1650: .It Fl K Ar key
1651: The actual
1652: .Ar key
1653: to use:
1654: this must be represented as a string comprised only of hex digits.
1.49 jmc 1655: If only the key is specified,
1656: the IV must also be specified using the
1.1 jsing 1657: .Fl iv
1658: option.
1659: When both a
1660: .Ar key
1661: and a
1662: .Ar password
1663: are specified, the
1664: .Ar key
1665: given with the
1666: .Fl K
1.49 jmc 1667: option will be used and the IV generated from the password will be taken.
1.1 jsing 1668: It probably does not make much sense to specify both
1669: .Ar key
1670: and
1671: .Ar password .
1672: .It Fl k Ar password
1673: The
1674: .Ar password
1675: to derive the key from.
1676: Superseded by the
1677: .Fl pass
1678: option.
1679: .It Fl kfile Ar file
1680: Read the password to derive the key from the first line of
1681: .Ar file .
1682: Superseded by the
1683: .Fl pass
1684: option.
1685: .It Fl md Ar digest
1686: Use
1687: .Ar digest
1688: to create a key from a pass phrase.
1689: .Ar digest
1690: may be one of
1.49 jmc 1691: .Cm md5
1.1 jsing 1692: or
1.49 jmc 1693: .Cm sha1 .
1.1 jsing 1694: .It Fl none
1695: Use NULL cipher (no encryption or decryption of input).
1696: .It Fl nopad
1697: Disable standard block padding.
1698: .It Fl nosalt
1.49 jmc 1699: Don't use a salt in the key derivation routines.
1.1 jsing 1700: This option should
1701: .Em NEVER
1.49 jmc 1702: be used
1703: since it makes it possible to perform efficient dictionary
1704: attacks on the password and to attack stream cipher encrypted data.
1.1 jsing 1705: .It Fl out Ar file
1.51 jmc 1706: The output file to write to,
1.57 jmc 1707: or standard output if not specified.
1.1 jsing 1708: .It Fl P
1.49 jmc 1709: Print out the salt, key, and IV used, then immediately exit;
1.1 jsing 1710: don't do any encryption or decryption.
1711: .It Fl p
1.49 jmc 1712: Print out the salt, key, and IV used.
1.1 jsing 1713: .It Fl pass Ar arg
1714: The password source.
1715: .It Fl S Ar salt
1716: The actual
1717: .Ar salt
1718: to use:
1719: this must be represented as a string comprised only of hex digits.
1720: .It Fl salt
1.49 jmc 1721: Use a salt in the key derivation routines (the default).
1722: When the salt is being used
1723: the first eight bytes of the encrypted data are reserved for the salt:
1724: it is randomly generated when encrypting a file and read from the
1725: encrypted file when it is decrypted.
1.1 jsing 1726: .El
1727: .Sh ERRSTR
1728: .Nm openssl errstr
1729: .Op Fl stats
1730: .Ar errno ...
1731: .Pp
1732: The
1733: .Nm errstr
1734: command performs error number to error string conversion,
1735: generating a human-readable string representing the error code
1736: .Ar errno .
1737: The string is obtained through the
1738: .Xr ERR_error_string_n 3
1739: function and has the following format:
1740: .Pp
1741: .Dl error:[error code]:[library name]:[function name]:[reason string]
1742: .Pp
1743: .Bq error code
1744: is an 8-digit hexadecimal number.
1745: The remaining fields
1746: .Bq library name ,
1747: .Bq function name ,
1748: and
1749: .Bq reason string
1750: are all ASCII text.
1751: .Pp
1752: The options are as follows:
1753: .Bl -tag -width Ds
1754: .It Fl stats
1755: Print debugging statistics about various aspects of the hash table.
1756: .El
1757: .Sh GENDSA
1758: .nr nS 1
1759: .Nm "openssl gendsa"
1760: .Oo
1761: .Fl aes128 | aes192 | aes256 |
1762: .Fl des | des3
1763: .Oc
1764: .Op Fl out Ar file
1765: .Op Ar paramfile
1766: .nr nS 0
1767: .Pp
1768: The
1769: .Nm gendsa
1770: command generates a DSA private key from a DSA parameter file
1.51 jmc 1771: (typically generated by the
1.1 jsing 1772: .Nm openssl dsaparam
1773: command).
1.51 jmc 1774: DSA key generation is little more than random number generation so it is
1775: much quicker than,
1776: for example,
1777: RSA key generation.
1.1 jsing 1778: .Pp
1779: The options are as follows:
1780: .Bl -tag -width Ds
1781: .It Xo
1782: .Fl aes128 | aes192 | aes256 |
1783: .Fl des | des3
1784: .Xc
1.51 jmc 1785: Encrypt the private key with the AES, DES,
1.1 jsing 1786: or the triple DES ciphers, respectively, before outputting it.
1787: A pass phrase is prompted for.
1788: If none of these options are specified, no encryption is used.
1789: .It Fl out Ar file
1.51 jmc 1790: The output file to write to,
1.57 jmc 1791: or standard output if not specified.
1.1 jsing 1792: .It Ar paramfile
1.51 jmc 1793: Specify the DSA parameter file to use.
1.1 jsing 1794: The parameters in this file determine the size of the private key.
1795: .El
1796: .Sh GENPKEY
1797: .nr nS 1
1798: .Nm "openssl genpkey"
1799: .Op Fl algorithm Ar alg
1800: .Op Ar cipher
1801: .Op Fl genparam
1802: .Op Fl out Ar file
1.52 jmc 1803: .Op Fl outform Cm der | pem
1.1 jsing 1804: .Op Fl paramfile Ar file
1805: .Op Fl pass Ar arg
1806: .Op Fl pkeyopt Ar opt : Ns Ar value
1807: .Op Fl text
1808: .nr nS 0
1809: .Pp
1810: The
1811: .Nm genpkey
1812: command generates private keys.
1813: The use of this
1814: program is encouraged over the algorithm specific utilities
1.22 bcook 1815: because additional algorithm options can be used.
1.1 jsing 1816: .Pp
1817: The options are as follows:
1818: .Bl -tag -width Ds
1819: .It Fl algorithm Ar alg
1820: The public key algorithm to use,
1821: such as RSA, DSA, or DH.
1.52 jmc 1822: This option must precede any
1.1 jsing 1823: .Fl pkeyopt
1824: options.
1825: The options
1826: .Fl paramfile
1827: and
1828: .Fl algorithm
1829: are mutually exclusive.
1830: .It Ar cipher
1831: Encrypt the private key with the supplied cipher.
1832: Any algorithm name accepted by
1.52 jmc 1833: .Xr EVP_get_cipherbyname 3
1834: is acceptable.
1.1 jsing 1835: .It Fl genparam
1836: Generate a set of parameters instead of a private key.
1.52 jmc 1837: This option must precede any
1.1 jsing 1838: .Fl algorithm ,
1839: .Fl paramfile ,
1840: or
1841: .Fl pkeyopt
1842: options.
1843: .It Fl out Ar file
1.52 jmc 1844: The output file to write to,
1.57 jmc 1845: or standard output if not specified.
1.52 jmc 1846: .It Fl outform Cm der | pem
1847: The output format.
1.1 jsing 1848: .It Fl paramfile Ar file
1.52 jmc 1849: Some public key algorithms generate a private key based on a set of parameters,
1850: which can be supplied using this option.
1.1 jsing 1851: If this option is used the public key
1852: algorithm used is determined by the parameters.
1.52 jmc 1853: This option must precede any
1.1 jsing 1854: .Fl pkeyopt
1855: options.
1856: The options
1857: .Fl paramfile
1858: and
1859: .Fl algorithm
1860: are mutually exclusive.
1861: .It Fl pass Ar arg
1862: The output file password source.
1863: .It Fl pkeyopt Ar opt : Ns Ar value
1864: Set the public key algorithm option
1865: .Ar opt
1866: to
1.52 jmc 1867: .Ar value ,
1868: as follows:
1.1 jsing 1869: .Bl -tag -width Ds -offset indent
1870: .It rsa_keygen_bits : Ns Ar numbits
1871: (RSA)
1872: The number of bits in the generated key.
1.52 jmc 1873: The default is 2048.
1.1 jsing 1874: .It rsa_keygen_pubexp : Ns Ar value
1875: (RSA)
1876: The RSA public exponent value.
1877: This can be a large decimal or hexadecimal value if preceded by 0x.
1.52 jmc 1878: The default is 65537.
1.1 jsing 1879: .It dsa_paramgen_bits : Ns Ar numbits
1880: (DSA)
1881: The number of bits in the generated parameters.
1.52 jmc 1882: The default is 1024.
1.1 jsing 1883: .It dh_paramgen_prime_len : Ns Ar numbits
1884: (DH)
1885: The number of bits in the prime parameter
1886: .Ar p .
1887: .It dh_paramgen_generator : Ns Ar value
1888: (DH)
1889: The value to use for the generator
1890: .Ar g .
1891: .It ec_paramgen_curve : Ns Ar curve
1892: (EC)
1893: The EC curve to use.
1894: .El
1.52 jmc 1895: .It Fl text
1.64 jmc 1896: Print the private/public key in plain text.
1.52 jmc 1897: .El
1.1 jsing 1898: .Sh GENRSA
1899: .nr nS 1
1900: .Nm "openssl genrsa"
1901: .Op Fl 3 | f4
1.53 jmc 1902: .Op Fl aes128 | aes192 | aes256 | des | des3
1.1 jsing 1903: .Op Fl out Ar file
1904: .Op Fl passout Ar arg
1905: .Op Ar numbits
1906: .nr nS 0
1907: .Pp
1908: The
1909: .Nm genrsa
1.53 jmc 1910: command generates an RSA private key,
1911: which essentially involves the generation of two prime numbers.
1912: When generating the key,
1913: various symbols will be output to indicate the progress of the generation.
1914: A
1915: .Sq \&.
1916: represents each number which has passed an initial sieve test;
1917: .Sq +
1918: means a number has passed a single round of the Miller-Rabin primality test.
1919: A newline means that the number has passed all the prime tests
1920: (the actual number depends on the key size).
1.1 jsing 1921: .Pp
1922: The options are as follows:
1923: .Bl -tag -width Ds
1924: .It Fl 3 | f4
1925: The public exponent to use, either 3 or 65537.
1926: The default is 65537.
1.53 jmc 1927: .It Fl aes128 | aes192 | aes256 | des | des3
1928: Encrypt the private key with the AES, DES,
1.1 jsing 1929: or the triple DES ciphers, respectively, before outputting it.
1930: If none of these options are specified, no encryption is used.
1931: If encryption is used, a pass phrase is prompted for,
1932: if it is not supplied via the
1933: .Fl passout
1934: option.
1935: .It Fl out Ar file
1.53 jmc 1936: The output file to write to,
1.57 jmc 1937: or standard output if not specified.
1.1 jsing 1938: .It Fl passout Ar arg
1939: The output file password source.
1940: .It Ar numbits
1941: The size of the private key to generate in bits.
1942: This must be the last option specified.
1943: The default is 2048.
1944: .El
1945: .Sh NSEQ
1946: .Nm openssl nseq
1947: .Op Fl in Ar file
1948: .Op Fl out Ar file
1949: .Op Fl toseq
1950: .Pp
1951: The
1952: .Nm nseq
1.54 jmc 1953: command takes a file containing a Netscape certificate sequence
1954: (an alternative to the standard PKCS#7 format)
1955: and prints out the certificates contained in it,
1956: or takes a file of certificates
1957: and converts it into a Netscape certificate sequence.
1958: .Pp
1959: The PEM-encoded form uses the same headers and footers as a certificate:
1960: .Bd -unfilled -offset indent
1961: -----BEGIN CERTIFICATE-----
1962: -----END CERTIFICATE-----
1963: .Ed
1.1 jsing 1964: .Pp
1965: The options are as follows:
1966: .Bl -tag -width Ds
1967: .It Fl in Ar file
1.54 jmc 1968: The input file to read from,
1969: or standard input if not specified.
1.1 jsing 1970: .It Fl out Ar file
1.54 jmc 1971: The output file to write to,
1972: or standard output if not specified.
1.1 jsing 1973: .It Fl toseq
1974: Normally, a Netscape certificate sequence will be input and the output
1975: is the certificates contained in it.
1976: With the
1977: .Fl toseq
1978: option the situation is reversed:
1979: a Netscape certificate sequence is created from a file of certificates.
1980: .El
1981: .Sh OCSP
1982: .nr nS 1
1983: .Nm "openssl ocsp"
1984: .Op Fl CA Ar file
1985: .Op Fl CAfile Ar file
1986: .Op Fl CApath Ar directory
1987: .Op Fl cert Ar file
1988: .Op Fl dgst Ar alg
1.55 jmc 1989: .Op Fl host Ar hostname : Ns Ar port
1.1 jsing 1990: .Op Fl index Ar indexfile
1991: .Op Fl issuer Ar file
1992: .Op Fl ndays Ar days
1993: .Op Fl nmin Ar minutes
1994: .Op Fl no_cert_checks
1995: .Op Fl no_cert_verify
1996: .Op Fl no_certs
1997: .Op Fl no_chain
1998: .Op Fl no_intern
1999: .Op Fl no_nonce
2000: .Op Fl no_signature_verify
2001: .Op Fl nonce
2002: .Op Fl noverify
2003: .Op Fl nrequest Ar number
2004: .Op Fl out Ar file
2005: .Op Fl path Ar path
2006: .Op Fl port Ar portnum
2007: .Op Fl req_text
2008: .Op Fl reqin Ar file
2009: .Op Fl reqout Ar file
2010: .Op Fl resp_key_id
2011: .Op Fl resp_no_certs
2012: .Op Fl resp_text
2013: .Op Fl respin Ar file
2014: .Op Fl respout Ar file
2015: .Op Fl rkey Ar file
2016: .Op Fl rother Ar file
2017: .Op Fl rsigner Ar file
2018: .Op Fl serial Ar number
2019: .Op Fl sign_other Ar file
2020: .Op Fl signer Ar file
2021: .Op Fl signkey Ar file
2022: .Op Fl status_age Ar age
2023: .Op Fl text
2024: .Op Fl trust_other
2025: .Op Fl url Ar responder_url
2026: .Op Fl VAfile Ar file
2027: .Op Fl validity_period Ar nsec
2028: .Op Fl verify_other Ar file
2029: .nr nS 0
2030: .Pp
1.55 jmc 2031: The Online Certificate Status Protocol (OCSP)
2032: enables applications to determine the (revocation) state
2033: of an identified certificate (RFC 2560).
1.1 jsing 2034: .Pp
2035: The
2036: .Nm ocsp
2037: command performs many common OCSP tasks.
2038: It can be used to print out requests and responses,
2039: create requests and send queries to an OCSP responder,
2040: and behave like a mini OCSP server itself.
2041: .Pp
2042: The options are as follows:
2043: .Bl -tag -width Ds
2044: .It Fl CAfile Ar file , Fl CApath Ar directory
1.55 jmc 2045: A file or path containing trusted CA certificates,
2046: used to verify the signature on the OCSP response.
1.1 jsing 2047: .It Fl cert Ar file
2048: Add the certificate
2049: .Ar file
2050: to the request.
2051: The issuer certificate is taken from the previous
2052: .Fl issuer
2053: option, or an error occurs if no issuer certificate is specified.
2054: .It Fl dgst Ar alg
1.55 jmc 2055: Use the digest algorithm
2056: .Ar alg
2057: for certificate identification in the OCSP request.
1.1 jsing 2058: By default SHA-1 is used.
2059: .It Xo
2060: .Fl host Ar hostname : Ns Ar port ,
2061: .Fl path Ar path
2062: .Xc
1.55 jmc 2063: Send
2064: the OCSP request to
1.1 jsing 2065: .Ar hostname
1.55 jmc 2066: on
1.1 jsing 2067: .Ar port .
2068: .Fl path
2069: specifies the HTTP path name to use, or
1.55 jmc 2070: .Pa /
1.1 jsing 2071: by default.
2072: .It Fl issuer Ar file
1.55 jmc 2073: The current issuer certificate,
2074: in PEM format.
2075: Can be used multiple times
2076: and must come before any
1.1 jsing 2077: .Fl cert
2078: options.
2079: .It Fl no_cert_checks
2080: Don't perform any additional checks on the OCSP response signer's certificate.
2081: That is, do not make any checks to see if the signer's certificate is
2082: authorised to provide the necessary status information:
2083: as a result this option should only be used for testing purposes.
2084: .It Fl no_cert_verify
2085: Don't verify the OCSP response signer's certificate at all.
2086: Since this option allows the OCSP response to be signed by any certificate,
2087: it should only be used for testing purposes.
2088: .It Fl no_certs
1.55 jmc 2089: Don't include any certificates in the signed request.
1.1 jsing 2090: .It Fl no_chain
2091: Do not use certificates in the response as additional untrusted CA
2092: certificates.
2093: .It Fl no_intern
2094: Ignore certificates contained in the OCSP response
2095: when searching for the signer's certificate.
1.55 jmc 2096: The signer's certificate must be specified with either the
1.1 jsing 2097: .Fl verify_other
2098: or
2099: .Fl VAfile
2100: options.
2101: .It Fl no_signature_verify
2102: Don't check the signature on the OCSP response.
2103: Since this option tolerates invalid signatures on OCSP responses,
2104: it will normally only be used for testing purposes.
2105: .It Fl nonce , no_nonce
1.55 jmc 2106: Add an OCSP nonce extension to a request,
2107: or disable an OCSP nonce addition.
1.1 jsing 2108: Normally, if an OCSP request is input using the
2109: .Fl respin
1.55 jmc 2110: option no nonce is added:
1.1 jsing 2111: using the
2112: .Fl nonce
1.55 jmc 2113: option will force the addition of a nonce.
1.1 jsing 2114: If an OCSP request is being created (using the
2115: .Fl cert
2116: and
2117: .Fl serial
2118: options)
1.55 jmc 2119: a nonce is automatically added; specifying
1.1 jsing 2120: .Fl no_nonce
2121: overrides this.
2122: .It Fl noverify
1.55 jmc 2123: Don't attempt to verify the OCSP response signature or the nonce values.
2124: This is normally only be used for debugging
1.1 jsing 2125: since it disables all verification of the responder's certificate.
2126: .It Fl out Ar file
1.55 jmc 2127: Specify the output file to write to,
1.57 jmc 2128: or standard output if not specified.
1.1 jsing 2129: .It Fl req_text , resp_text , text
2130: Print out the text form of the OCSP request, response, or both, respectively.
2131: .It Fl reqin Ar file , Fl respin Ar file
2132: Read an OCSP request or response file from
2133: .Ar file .
2134: These options are ignored
2135: if an OCSP request or response creation is implied by other options
2136: (for example with the
2137: .Fl serial , cert ,
2138: and
2139: .Fl host
2140: options).
2141: .It Fl reqout Ar file , Fl respout Ar file
2142: Write out the DER-encoded certificate request or response to
2143: .Ar file .
2144: .It Fl serial Ar num
2145: Same as the
2146: .Fl cert
2147: option except the certificate with serial number
2148: .Ar num
2149: is added to the request.
2150: The serial number is interpreted as a decimal integer unless preceded by
2151: .Sq 0x .
1.55 jmc 2152: Negative integers can also be specified
2153: by preceding the value with a minus sign.
1.1 jsing 2154: .It Fl sign_other Ar file
2155: Additional certificates to include in the signed request.
2156: .It Fl signer Ar file , Fl signkey Ar file
2157: Sign the OCSP request using the certificate specified in the
2158: .Fl signer
2159: option and the private key specified by the
2160: .Fl signkey
2161: option.
2162: If the
2163: .Fl signkey
2164: option is not present, then the private key is read from the same file
2165: as the certificate.
2166: If neither option is specified, the OCSP request is not signed.
2167: .It Fl trust_other
2168: The certificates specified by the
2169: .Fl verify_other
2170: option should be explicitly trusted and no additional checks will be
2171: performed on them.
2172: This is useful when the complete responder certificate chain is not available
2173: or trusting a root CA is not appropriate.
2174: .It Fl url Ar responder_url
2175: Specify the responder URL.
2176: Both HTTP and HTTPS
2177: .Pq SSL/TLS
2178: URLs can be specified.
2179: .It Fl VAfile Ar file
1.55 jmc 2180: A file containing explicitly trusted responder certificates.
1.1 jsing 2181: Equivalent to the
2182: .Fl verify_other
2183: and
2184: .Fl trust_other
2185: options.
2186: .It Fl validity_period Ar nsec , Fl status_age Ar age
1.55 jmc 2187: The range of times, in seconds, which will be tolerated in an OCSP response.
2188: Each certificate status response includes a notBefore time
2189: and an optional notAfter time.
1.1 jsing 2190: The current time should fall between these two values,
2191: but the interval between the two times may be only a few seconds.
2192: In practice the OCSP responder and clients' clocks may not be precisely
2193: synchronised and so such a check may fail.
2194: To avoid this the
2195: .Fl validity_period
2196: option can be used to specify an acceptable error range in seconds,
1.55 jmc 2197: the default value being 5 minutes.
1.1 jsing 2198: .Pp
1.55 jmc 2199: If the notAfter time is omitted from a response,
2200: it means that new status information is immediately available.
2201: In this case the age of the notBefore field is checked
2202: to see it is not older than
1.1 jsing 2203: .Ar age
2204: seconds old.
2205: By default, this additional check is not performed.
2206: .It Fl verify_other Ar file
1.55 jmc 2207: A file containing additional certificates to search
2208: when attempting to locate the OCSP response signing certificate.
2209: Some responders omit the actual signer's certificate from the response,
2210: so this can be used to supply the necessary certificate.
1.1 jsing 2211: .El
1.55 jmc 2212: .Pp
2213: The options for the OCSP server are as follows:
1.1 jsing 2214: .Bl -tag -width "XXXX"
2215: .It Fl CA Ar file
2216: CA certificate corresponding to the revocation information in
2217: .Ar indexfile .
2218: .It Fl index Ar indexfile
2219: .Ar indexfile
1.55 jmc 2220: is a text index file in ca format
2221: containing certificate revocation information.
1.1 jsing 2222: .Pp
1.55 jmc 2223: If this option is specified,
1.1 jsing 2224: .Nm ocsp
1.55 jmc 2225: is in responder mode, otherwise it is in client mode.
2226: The requests the responder processes can be either specified on
1.1 jsing 2227: the command line (using the
2228: .Fl issuer
2229: and
2230: .Fl serial
2231: options), supplied in a file (using the
2232: .Fl respin
1.55 jmc 2233: option), or via external OCSP clients (if
1.1 jsing 2234: .Ar port
2235: or
2236: .Ar url
2237: is specified).
2238: .Pp
1.55 jmc 2239: If this option is present, then the
1.1 jsing 2240: .Fl CA
2241: and
2242: .Fl rsigner
2243: options must also be present.
2244: .It Fl nmin Ar minutes , Fl ndays Ar days
2245: Number of
2246: .Ar minutes
2247: or
2248: .Ar days
1.55 jmc 2249: when fresh revocation information is available:
2250: used in the nextUpdate field.
2251: If neither option is present,
2252: the nextUpdate field is omitted,
2253: meaning fresh revocation information is immediately available.
1.1 jsing 2254: .It Fl nrequest Ar number
1.55 jmc 2255: Exit after receiving
1.1 jsing 2256: .Ar number
1.55 jmc 2257: requests (the default is unlimited).
1.1 jsing 2258: .It Fl port Ar portnum
2259: Port to listen for OCSP requests on.
1.55 jmc 2260: May also be specified using the
1.1 jsing 2261: .Fl url
2262: option.
2263: .It Fl resp_key_id
2264: Identify the signer certificate using the key ID;
1.55 jmc 2265: the default is to use the subject name.
1.1 jsing 2266: .It Fl resp_no_certs
2267: Don't include any certificates in the OCSP response.
2268: .It Fl rkey Ar file
2269: The private key to sign OCSP responses with;
2270: if not present, the file specified in the
2271: .Fl rsigner
2272: option is used.
2273: .It Fl rother Ar file
2274: Additional certificates to include in the OCSP response.
2275: .It Fl rsigner Ar file
2276: The certificate to sign OCSP responses with.
2277: .El
2278: .Pp
2279: Initially the OCSP responder certificate is located and the signature on
2280: the OCSP request checked using the responder certificate's public key.
2281: Then a normal certificate verify is performed on the OCSP responder certificate
2282: building up a certificate chain in the process.
2283: The locations of the trusted certificates used to build the chain can be
2284: specified by the
2285: .Fl CAfile
2286: and
2287: .Fl CApath
2288: options or they will be looked for in the standard
1.55 jmc 2289: .Nm openssl
2290: certificates directory.
1.1 jsing 2291: .Pp
1.55 jmc 2292: If the initial verify fails, the OCSP verify process halts with an error.
1.1 jsing 2293: Otherwise the issuing CA certificate in the request is compared to the OCSP
2294: responder certificate: if there is a match then the OCSP verify succeeds.
2295: .Pp
2296: Otherwise the OCSP responder certificate's CA is checked against the issuing
2297: CA certificate in the request.
2298: If there is a match and the OCSPSigning extended key usage is present
2299: in the OCSP responder certificate, then the OCSP verify succeeds.
2300: .Pp
2301: Otherwise the root CA of the OCSP responder's CA is checked to see if it
2302: is trusted for OCSP signing.
2303: If it is, the OCSP verify succeeds.
2304: .Pp
2305: If none of these checks is successful, the OCSP verify fails.
2306: What this effectively means is that if the OCSP responder certificate is
2307: authorised directly by the CA it is issuing revocation information about
1.55 jmc 2308: (and it is correctly configured),
1.1 jsing 2309: then verification will succeed.
2310: .Pp
1.55 jmc 2311: If the OCSP responder is a global responder,
2312: which can give details about multiple CAs
2313: and has its own separate certificate chain,
2314: then its root CA can be trusted for OCSP signing.
1.1 jsing 2315: For example:
2316: .Bd -literal -offset indent
2317: $ openssl x509 -in ocspCA.pem -addtrust OCSPSigning \e
2318: -out trustedCA.pem
2319: .Ed
2320: .Pp
2321: Alternatively, the responder certificate itself can be explicitly trusted
2322: with the
2323: .Fl VAfile
2324: option.
2325: .Sh PASSWD
2326: .nr nS 1
2327: .Nm "openssl passwd"
2328: .Op Fl 1 | apr1 | crypt
2329: .Op Fl in Ar file
2330: .Op Fl noverify
2331: .Op Fl quiet
2332: .Op Fl reverse
2333: .Op Fl salt Ar string
2334: .Op Fl stdin
2335: .Op Fl table
2336: .Op Ar password
2337: .nr nS 0
2338: .Pp
2339: The
2340: .Nm passwd
1.56 jmc 2341: command computes the hash of a password.
1.1 jsing 2342: .Pp
2343: The options are as follows:
2344: .Bl -tag -width Ds
2345: .It Fl 1
2346: Use the MD5 based
2347: .Bx
2348: password algorithm
1.56 jmc 2349: .Qq 1 .
1.1 jsing 2350: .It Fl apr1
2351: Use the
1.56 jmc 2352: .Qq apr1
1.1 jsing 2353: algorithm
1.56 jmc 2354: .Po
2355: Apache variant of the
1.1 jsing 2356: .Bx
1.56 jmc 2357: algorithm
2358: .Pc .
1.1 jsing 2359: .It Fl crypt
2360: Use the
1.56 jmc 2361: .Qq crypt
2362: algorithm (the default).
1.1 jsing 2363: .It Fl in Ar file
2364: Read passwords from
2365: .Ar file .
2366: .It Fl noverify
2367: Don't verify when reading a password from the terminal.
2368: .It Fl quiet
2369: Don't output warnings when passwords given on the command line are truncated.
2370: .It Fl reverse
2371: Switch table columns.
2372: This only makes sense in conjunction with the
2373: .Fl table
2374: option.
2375: .It Fl salt Ar string
1.56 jmc 2376: Use the salt specified by
2377: .Ar string .
1.1 jsing 2378: When reading a password from the terminal, this implies
2379: .Fl noverify .
2380: .It Fl stdin
1.56 jmc 2381: Read passwords from standard input.
1.1 jsing 2382: .It Fl table
2383: In the output list, prepend the cleartext password and a TAB character
2384: to each password hash.
2385: .El
2386: .Sh PKCS7
2387: .nr nS 1
2388: .Nm "openssl pkcs7"
2389: .Op Fl in Ar file
1.57 jmc 2390: .Op Fl inform Cm der | pem
1.1 jsing 2391: .Op Fl noout
2392: .Op Fl out Ar file
1.57 jmc 2393: .Op Fl outform Cm der | pem
1.1 jsing 2394: .Op Fl print_certs
2395: .Op Fl text
2396: .nr nS 0
2397: .Pp
2398: The
2399: .Nm pkcs7
2400: command processes PKCS#7 files in DER or PEM format.
1.57 jmc 2401: The PKCS#7 routines only understand PKCS#7 v 1.5 as specified in RFC 2315.
2402: They cannot currently parse, for example, the new CMS as described in RFC 2630.
2403: .Pp
1.1 jsing 2404: The options are as follows:
2405: .Bl -tag -width Ds
2406: .It Fl in Ar file
1.57 jmc 2407: The input file to read from,
2408: or standard input if not specified.
2409: .It Fl inform Cm der | pem
2410: The input format.
1.1 jsing 2411: .It Fl noout
2412: Don't output the encoded version of the PKCS#7 structure
2413: (or certificates if
2414: .Fl print_certs
2415: is set).
2416: .It Fl out Ar file
1.57 jmc 2417: The output to write to,
2418: or standard output if not specified.
2419: .It Fl outform Cm der | pem
2420: The output format.
1.1 jsing 2421: .It Fl print_certs
1.57 jmc 2422: Print any certificates or CRLs contained in the file,
2423: preceded by their subject and issuer names in a one-line format.
1.1 jsing 2424: .It Fl text
1.57 jmc 2425: Print certificate details in full rather than just subject and issuer names.
1.1 jsing 2426: .El
2427: .Sh PKCS8
2428: .nr nS 1
2429: .Nm "openssl pkcs8"
2430: .Op Fl embed
2431: .Op Fl in Ar file
1.58 jmc 2432: .Op Fl inform Cm der | pem
1.1 jsing 2433: .Op Fl nocrypt
2434: .Op Fl noiter
2435: .Op Fl nooct
2436: .Op Fl nsdb
2437: .Op Fl out Ar file
1.58 jmc 2438: .Op Fl outform Cm der | pem
1.1 jsing 2439: .Op Fl passin Ar arg
2440: .Op Fl passout Ar arg
2441: .Op Fl topk8
2442: .Op Fl v1 Ar alg
2443: .Op Fl v2 Ar alg
2444: .nr nS 0
2445: .Pp
2446: The
2447: .Nm pkcs8
1.58 jmc 2448: command processes private keys
2449: (both encrypted and unencrypted)
2450: in PKCS#8 format
2451: with a variety of PKCS#5 (v1.5 and v2.0) and PKCS#12 algorithms.
2452: The default encryption is only 56 bits;
2453: keys encrypted using PKCS#5 v2.0 algorithms and high iteration counts
2454: are more secure.
2455: .Pp
2456: The encrypted form of a PEM-encoded PKCS#8 file uses the following
2457: headers and footers:
2458: .Bd -unfilled -offset indent
2459: -----BEGIN ENCRYPTED PRIVATE KEY-----
2460: -----END ENCRYPTED PRIVATE KEY-----
2461: .Ed
2462: .Pp
2463: The unencrypted form uses:
2464: .Bd -unfilled -offset indent
2465: -----BEGIN PRIVATE KEY-----
2466: -----END PRIVATE KEY-----
2467: .Ed
1.1 jsing 2468: .Pp
2469: The options are as follows:
2470: .Bl -tag -width Ds
2471: .It Fl embed
1.58 jmc 2472: Generate DSA keys in a broken format.
2473: The DSA parameters are embedded inside the PrivateKey structure.
1.1 jsing 2474: In this form the OCTET STRING contains an ASN1 SEQUENCE consisting of
2475: two structures:
2476: a SEQUENCE containing the parameters and an ASN1 INTEGER containing
2477: the private key.
2478: .It Fl in Ar file
1.58 jmc 2479: The input file to read from,
2480: or standard input if not specified.
1.1 jsing 2481: If the key is encrypted, a pass phrase will be prompted for.
1.58 jmc 2482: .It Fl inform Cm der | pem
2483: The input format.
1.1 jsing 2484: .It Fl nocrypt
1.58 jmc 2485: Generate an unencrypted PrivateKeyInfo structure.
2486: This option does not encrypt private keys at all
2487: and should only be used when absolutely necessary.
1.1 jsing 2488: .It Fl noiter
2489: Use an iteration count of 1.
2490: See the
2491: .Sx PKCS12
2492: section below for a detailed explanation of this option.
2493: .It Fl nooct
1.58 jmc 2494: Generate RSA private keys in a broken format that some software uses.
1.1 jsing 2495: Specifically the private key should be enclosed in an OCTET STRING,
2496: but some software just includes the structure itself without the
2497: surrounding OCTET STRING.
2498: .It Fl nsdb
1.58 jmc 2499: Generate DSA keys in a broken format compatible with Netscape
1.1 jsing 2500: private key databases.
1.58 jmc 2501: The PrivateKey contains a SEQUENCE
2502: consisting of the public and private keys, respectively.
1.1 jsing 2503: .It Fl out Ar file
1.58 jmc 2504: The output file to write to,
2505: or standard output if none is specified.
1.1 jsing 2506: If any encryption options are set, a pass phrase will be prompted for.
1.58 jmc 2507: .It Fl outform Cm der | pem
2508: The output format.
1.1 jsing 2509: .It Fl passin Ar arg
2510: The key password source.
2511: .It Fl passout Ar arg
2512: The output file password source.
2513: .It Fl topk8
1.58 jmc 2514: Read a traditional format private key and write a PKCS#8 format key.
1.1 jsing 2515: .It Fl v1 Ar alg
1.58 jmc 2516: Specify a PKCS#5 v1.5 or PKCS#12 algorithm to use.
2517: .Pp
2518: .Bl -tag -width "XXXX" -compact
2519: .It PBE-MD5-DES
2520: 56-bit DES.
2521: .It PBE-SHA1-RC2-64 | PBE-MD5-RC2-64 | PBE-SHA1-DES
2522: 64-bit RC2 or 56-bit DES.
2523: .It PBE-SHA1-RC4-128 | PBE-SHA1-RC4-40 | PBE-SHA1-3DES
2524: .It PBE-SHA1-2DES | PBE-SHA1-RC2-128 | PBE-SHA1-RC2-40
2525: PKCS#12 password-based encryption algorithm,
2526: which allow strong encryption algorithms like triple DES or 128-bit RC2.
2527: .El
1.1 jsing 2528: .It Fl v2 Ar alg
1.58 jmc 2529: Use PKCS#5 v2.0 algorithms.
2530: Supports algorithms such as 168-bit triple DES or 128-bit RC2,
2531: however not many implementations support PKCS#5 v2.0 yet
2532: (if using private keys with
2533: .Nm openssl
2534: this doesn't matter).
1.1 jsing 2535: .Pp
2536: .Ar alg
1.58 jmc 2537: is the encryption algorithm to use;
2538: valid values include des, des3, and rc2.
2539: It is recommended that des3 is used.
1.1 jsing 2540: .El
2541: .Sh PKCS12
2542: .nr nS 1
2543: .Nm "openssl pkcs12"
1.59 jmc 2544: .Op Fl aes128 | aes192 | aes256 | des | des3
1.1 jsing 2545: .Op Fl cacerts
2546: .Op Fl CAfile Ar file
2547: .Op Fl caname Ar name
2548: .Op Fl CApath Ar directory
2549: .Op Fl certfile Ar file
2550: .Op Fl certpbe Ar alg
2551: .Op Fl chain
2552: .Op Fl clcerts
2553: .Op Fl CSP Ar name
2554: .Op Fl descert
2555: .Op Fl export
2556: .Op Fl in Ar file
2557: .Op Fl info
2558: .Op Fl inkey Ar file
2559: .Op Fl keyex
2560: .Op Fl keypbe Ar alg
2561: .Op Fl keysig
2562: .Op Fl macalg Ar alg
2563: .Op Fl maciter
2564: .Op Fl name Ar name
2565: .Op Fl nocerts
2566: .Op Fl nodes
2567: .Op Fl noiter
2568: .Op Fl nokeys
2569: .Op Fl nomac
2570: .Op Fl nomaciter
2571: .Op Fl nomacver
2572: .Op Fl noout
2573: .Op Fl out Ar file
2574: .Op Fl passin Ar arg
2575: .Op Fl passout Ar arg
2576: .Op Fl twopass
2577: .nr nS 0
2578: .Pp
2579: The
2580: .Nm pkcs12
2581: command allows PKCS#12 files
2582: .Pq sometimes referred to as PFX files
2583: to be created and parsed.
2584: By default, a PKCS#12 file is parsed;
2585: a PKCS#12 file can be created by using the
2586: .Fl export
1.59 jmc 2587: option.
2588: .Pp
2589: The options for parsing a PKCS12 file are as follows:
1.1 jsing 2590: .Bl -tag -width "XXXX"
1.59 jmc 2591: .It Fl aes128 | aes192 | aes256 | des | des3
2592: Encrypt private keys
2593: using AES, DES, or triple DES, respectively.
1.1 jsing 2594: The default is triple DES.
2595: .It Fl cacerts
2596: Only output CA certificates
2597: .Pq not client certificates .
2598: .It Fl clcerts
2599: Only output client certificates
2600: .Pq not CA certificates .
2601: .It Fl in Ar file
1.59 jmc 2602: The input file to read from,
2603: or standard input if not specified.
1.1 jsing 2604: .It Fl info
2605: Output additional information about the PKCS#12 file structure,
2606: algorithms used, and iteration counts.
2607: .It Fl nocerts
1.59 jmc 2608: Do not output certificates.
1.1 jsing 2609: .It Fl nodes
1.59 jmc 2610: Do not encrypt private keys.
1.1 jsing 2611: .It Fl nokeys
1.59 jmc 2612: Do not output private keys.
1.1 jsing 2613: .It Fl nomacver
1.59 jmc 2614: Do not attempt to verify the integrity MAC before reading the file.
1.1 jsing 2615: .It Fl noout
1.59 jmc 2616: Do not output the keys and certificates to the output file
1.1 jsing 2617: version of the PKCS#12 file.
2618: .It Fl out Ar file
1.59 jmc 2619: The output file to write to,
2620: or standard output if not specified.
1.1 jsing 2621: .It Fl passin Ar arg
2622: The key password source.
2623: .It Fl passout Ar arg
2624: The output file password source.
2625: .It Fl twopass
2626: Prompt for separate integrity and encryption passwords: most software
2627: always assumes these are the same so this option will render such
2628: PKCS#12 files unreadable.
2629: .El
1.59 jmc 2630: .Pp
2631: The options for PKCS12 file creation are as follows:
1.1 jsing 2632: .Bl -tag -width "XXXX"
2633: .It Fl CAfile Ar file
2634: CA storage as a file.
2635: .It Fl CApath Ar directory
2636: CA storage as a directory.
1.59 jmc 2637: The directory must be a standard certificate directory:
1.1 jsing 2638: that is, a hash of each subject name (using
1.59 jmc 2639: .Nm x509 Fl hash )
1.1 jsing 2640: should be linked to each certificate.
2641: .It Fl caname Ar name
1.59 jmc 2642: Specify the
1.1 jsing 2643: .Qq friendly name
2644: for other certificates.
1.59 jmc 2645: May be used multiple times to specify names for all certificates
1.1 jsing 2646: in the order they appear.
2647: .It Fl certfile Ar file
2648: A file to read additional certificates from.
2649: .It Fl certpbe Ar alg , Fl keypbe Ar alg
1.59 jmc 2650: Specify the algorithm used to encrypt the private key and
1.1 jsing 2651: certificates to be selected.
1.59 jmc 2652: Any PKCS#5 v1.5 or PKCS#12 PBE algorithm name can be used.
1.1 jsing 2653: If a cipher name
2654: (as output by the
2655: .Cm list-cipher-algorithms
2656: command) is specified then it
2657: is used with PKCS#5 v2.0.
2658: For interoperability reasons it is advisable to only use PKCS#12 algorithms.
2659: .It Fl chain
1.59 jmc 2660: Include the entire certificate chain of the user certificate.
1.1 jsing 2661: The standard CA store is used for this search.
2662: If the search fails, it is considered a fatal error.
2663: .It Fl CSP Ar name
2664: Write
2665: .Ar name
2666: as a Microsoft CSP name.
2667: .It Fl descert
2668: Encrypt the certificate using triple DES; this may render the PKCS#12
2669: file unreadable by some
2670: .Qq export grade
2671: software.
2672: By default, the private key is encrypted using triple DES and the
2673: certificate using 40-bit RC2.
2674: .It Fl export
1.59 jmc 2675: Create a PKCS#12 file (rather than parsing one).
1.1 jsing 2676: .It Fl in Ar file
1.59 jmc 2677: The input file to read from,
2678: or standard input if not specified,
2679: in PEM format.
1.1 jsing 2680: The order doesn't matter but one private key and its corresponding
2681: certificate should be present.
2682: If additional certificates are present, they will also be included
2683: in the PKCS#12 file.
2684: .It Fl inkey Ar file
1.59 jmc 2685: File to read a private key from.
1.1 jsing 2686: If not present, a private key must be present in the input file.
2687: .It Fl keyex | keysig
1.59 jmc 2688: Specify whether the private key is to be used for key exchange or just signing.
1.1 jsing 2689: Normally,
2690: .Qq export grade
2691: software will only allow 512-bit RSA keys to be
2692: used for encryption purposes, but arbitrary length keys for signing.
2693: The
2694: .Fl keysig
2695: option marks the key for signing only.
2696: Signing only keys can be used for S/MIME signing, authenticode
1.66 jmc 2697: (ActiveX control signing)
1.59 jmc 2698: and SSL client authentication.
1.1 jsing 2699: .It Fl macalg Ar alg
2700: Specify the MAC digest algorithm.
1.59 jmc 2701: The default is SHA1.
1.1 jsing 2702: .It Fl maciter
1.66 jmc 2703: Included for compatibility only:
1.59 jmc 2704: it used to be needed to use MAC iterations counts
2705: but they are now used by default.
1.1 jsing 2706: .It Fl name Ar name
1.59 jmc 2707: Specify the
1.1 jsing 2708: .Qq friendly name
2709: for the certificate and private key.
2710: This name is typically displayed in list boxes by software importing the file.
2711: .It Fl nomac
2712: Don't attempt to provide the MAC integrity.
2713: .It Fl nomaciter , noiter
1.59 jmc 2714: Affect the iteration counts on the MAC and key algorithms.
1.1 jsing 2715: Unless you wish to produce files compatible with MSIE 4.0, you should leave
2716: these options alone.
2717: .Pp
2718: To discourage attacks by using large dictionaries of common passwords,
2719: the algorithm that derives keys from passwords can have an iteration count
2720: applied to it: this causes a certain part of the algorithm to be repeated
2721: and slows it down.
2722: The MAC is used to check the file integrity but since it will normally
2723: have the same password as the keys and certificates it could also be attacked.
2724: By default, both MAC and encryption iteration counts are set to 2048;
2725: using these options the MAC and encryption iteration counts can be set to 1.
2726: Since this reduces the file security you should not use these options
2727: unless you really have to.
2728: Most software supports both MAC and key iteration counts.
2729: MSIE 4.0 doesn't support MAC iteration counts, so it needs the
2730: .Fl nomaciter
2731: option.
2732: .It Fl out Ar file
1.59 jmc 2733: The output file to write to,
2734: or standard output if not specified.
1.1 jsing 2735: .It Fl passin Ar arg
2736: The key password source.
2737: .It Fl passout Ar arg
2738: The output file password source.
2739: .El
2740: .Sh PKEY
2741: .nr nS 1
2742: .Nm "openssl pkey"
2743: .Op Ar cipher
2744: .Op Fl in Ar file
1.60 jmc 2745: .Op Fl inform Cm der | pem
1.1 jsing 2746: .Op Fl noout
2747: .Op Fl out Ar file
1.60 jmc 2748: .Op Fl outform Cm der | pem
1.1 jsing 2749: .Op Fl passin Ar arg
2750: .Op Fl passout Ar arg
2751: .Op Fl pubin
2752: .Op Fl pubout
2753: .Op Fl text
2754: .Op Fl text_pub
2755: .nr nS 0
2756: .Pp
2757: The
2758: .Nm pkey
2759: command processes public or private keys.
2760: They can be converted between various forms
2761: and their components printed out.
2762: .Pp
2763: The options are as follows:
2764: .Bl -tag -width Ds
2765: .It Ar cipher
1.60 jmc 2766: Encrypt the private key with the specified cipher.
1.1 jsing 2767: Any algorithm name accepted by
1.60 jmc 2768: .Xr EVP_get_cipherbyname 3
1.1 jsing 2769: is acceptable, such as
2770: .Cm des3 .
2771: .It Fl in Ar file
1.60 jmc 2772: The input file to read from,
2773: or standard input if not specified.
1.1 jsing 2774: If the key is encrypted a pass phrase will be prompted for.
1.60 jmc 2775: .It Fl inform Cm der | pem
2776: The input format.
1.1 jsing 2777: .It Fl noout
2778: Do not output the encoded version of the key.
2779: .It Fl out Ar file
1.60 jmc 2780: The output file to write to,
2781: or standard output if not specified.
1.1 jsing 2782: If any encryption options are set then a pass phrase
2783: will be prompted for.
1.60 jmc 2784: .It Fl outform Cm der | pem
2785: The output format.
1.1 jsing 2786: .It Fl passin Ar arg
2787: The key password source.
2788: .It Fl passout Ar arg
2789: The output file password source.
2790: .It Fl pubin
1.60 jmc 2791: Read in a public key, not a private key.
1.1 jsing 2792: .It Fl pubout
1.60 jmc 2793: Output a public key, not a private key.
2794: Automatically set if the input is a public key.
1.1 jsing 2795: .It Fl text
1.64 jmc 2796: Print the public/private key in plain text.
1.1 jsing 2797: .It Fl text_pub
2798: Print out only public key components
2799: even if a private key is being processed.
2800: .El
2801: .Sh PKEYPARAM
2802: .Cm openssl pkeyparam
2803: .Op Fl in Ar file
2804: .Op Fl noout
2805: .Op Fl out Ar file
2806: .Op Fl text
2807: .Pp
2808: The
1.61 jmc 2809: .Nm pkeyparam
1.1 jsing 2810: command processes public or private keys.
1.61 jmc 2811: The key type is determined by the PEM headers.
1.1 jsing 2812: .Pp
2813: The options are as follows:
2814: .Bl -tag -width Ds
2815: .It Fl in Ar file
1.61 jmc 2816: The input file to read from,
2817: or standard input if not specified.
1.1 jsing 2818: .It Fl noout
2819: Do not output the encoded version of the parameters.
2820: .It Fl out Ar file
1.61 jmc 2821: The output file to write to,
2822: or standard output if not specified.
1.1 jsing 2823: .It Fl text
1.64 jmc 2824: Print the parameters in plain text.
1.1 jsing 2825: .El
2826: .Sh PKEYUTL
2827: .nr nS 1
2828: .Nm "openssl pkeyutl"
2829: .Op Fl asn1parse
2830: .Op Fl certin
2831: .Op Fl decrypt
2832: .Op Fl derive
2833: .Op Fl encrypt
2834: .Op Fl hexdump
2835: .Op Fl in Ar file
2836: .Op Fl inkey Ar file
1.62 jmc 2837: .Op Fl keyform Cm der | pem
1.1 jsing 2838: .Op Fl out Ar file
2839: .Op Fl passin Ar arg
1.62 jmc 2840: .Op Fl peerform Cm der | pem
1.1 jsing 2841: .Op Fl peerkey Ar file
2842: .Op Fl pkeyopt Ar opt : Ns Ar value
2843: .Op Fl pubin
2844: .Op Fl rev
2845: .Op Fl sigfile Ar file
2846: .Op Fl sign
2847: .Op Fl verify
2848: .Op Fl verifyrecover
2849: .nr nS 0
2850: .Pp
2851: The
2852: .Nm pkeyutl
2853: command can be used to perform public key operations using
2854: any supported algorithm.
2855: .Pp
2856: The options are as follows:
2857: .Bl -tag -width Ds
2858: .It Fl asn1parse
2859: ASN1parse the output data.
2860: This is useful when combined with the
2861: .Fl verifyrecover
2862: option when an ASN1 structure is signed.
2863: .It Fl certin
2864: The input is a certificate containing a public key.
2865: .It Fl decrypt
2866: Decrypt the input data using a private key.
2867: .It Fl derive
2868: Derive a shared secret using the peer key.
2869: .It Fl encrypt
2870: Encrypt the input data using a public key.
2871: .It Fl hexdump
2872: Hex dump the output data.
2873: .It Fl in Ar file
1.62 jmc 2874: The input file to read from,
2875: or standard input if not specified.
1.1 jsing 2876: .It Fl inkey Ar file
2877: The input key file.
2878: By default it should be a private key.
1.62 jmc 2879: .It Fl keyform Cm der | pem
2880: The key format.
1.1 jsing 2881: .It Fl out Ar file
1.62 jmc 2882: The output file to write to,
2883: or standard output if not specified.
1.1 jsing 2884: .It Fl passin Ar arg
2885: The key password source.
1.62 jmc 2886: .It Fl peerform Cm der | pem
2887: The peer key format.
1.1 jsing 2888: .It Fl peerkey Ar file
2889: The peer key file, used by key derivation (agreement) operations.
2890: .It Fl pkeyopt Ar opt : Ns Ar value
1.62 jmc 2891: Set the public key algorithm option
2892: .Ar opt
2893: to
2894: .Ar value .
2895: Unless otherwise mentioned, all algorithms support the format
2896: .Ar digest : Ns Ar alg ,
2897: which specifies the digest to use
1.1 jsing 2898: for sign, verify, and verifyrecover operations.
2899: The value
2900: .Ar alg
2901: should represent a digest name as used in the
1.62 jmc 2902: .Xr EVP_get_digestbyname 3
2903: function.
2904: .Pp
1.1 jsing 2905: The RSA algorithm supports the
2906: encrypt, decrypt, sign, verify, and verifyrecover operations in general.
2907: Some padding modes only support some of these
2908: operations however.
2909: .Bl -tag -width Ds
2910: .It rsa_padding_mode : Ns Ar mode
2911: This sets the RSA padding mode.
2912: Acceptable values for
2913: .Ar mode
2914: are
2915: .Cm pkcs1
2916: for PKCS#1 padding;
2917: .Cm none
2918: for no padding;
2919: .Cm oaep
2920: for OAEP mode;
2921: .Cm x931
2922: for X9.31 mode;
2923: and
2924: .Cm pss
2925: for PSS.
2926: .Pp
2927: In PKCS#1 padding if the message digest is not set then the supplied data is
2928: signed or verified directly instead of using a DigestInfo structure.
2929: If a digest is set then a DigestInfo
2930: structure is used and its length
2931: must correspond to the digest type.
2932: For oeap mode only encryption and decryption is supported.
2933: For x931 if the digest type is set it is used to format the block data;
2934: otherwise the first byte is used to specify the X9.31 digest ID.
2935: Sign, verify, and verifyrecover can be performed in this mode.
2936: For pss mode only sign and verify are supported and the digest type must be
2937: specified.
2938: .It rsa_pss_saltlen : Ns Ar len
2939: For pss
2940: mode only this option specifies the salt length.
2941: Two special values are supported:
2942: -1 sets the salt length to the digest length.
2943: When signing -2 sets the salt length to the maximum permissible value.
2944: When verifying -2 causes the salt length to be automatically determined
2945: based on the PSS block structure.
2946: .El
1.62 jmc 2947: .Pp
1.1 jsing 2948: The DSA algorithm supports the sign and verify operations.
2949: Currently there are no additional options other than
2950: .Ar digest .
2951: Only the SHA1 digest can be used and this digest is assumed by default.
1.62 jmc 2952: .Pp
1.1 jsing 2953: The DH algorithm supports the derive operation
2954: and no additional options.
1.62 jmc 2955: .Pp
1.1 jsing 2956: The EC algorithm supports the sign, verify, and derive operations.
2957: The sign and verify operations use ECDSA and derive uses ECDH.
2958: Currently there are no additional options other than
2959: .Ar digest .
2960: Only the SHA1 digest can be used and this digest is assumed by default.
1.62 jmc 2961: .It Fl pubin
2962: The input file is a public key.
2963: .It Fl rev
2964: Reverse the order of the input buffer.
2965: .It Fl sigfile Ar file
2966: Signature file (verify operation only).
2967: .It Fl sign
2968: Sign the input data and output the signed result.
2969: This requires a private key.
2970: .It Fl verify
2971: Verify the input data against the signature file and indicate if the
2972: verification succeeded or failed.
2973: .It Fl verifyrecover
2974: Verify the input data and output the recovered data.
2975: .El
1.1 jsing 2976: .Sh PRIME
2977: .Cm openssl prime
2978: .Op Fl bits Ar n
2979: .Op Fl checks Ar n
2980: .Op Fl generate
2981: .Op Fl hex
2982: .Op Fl safe
2983: .Ar p
2984: .Pp
2985: The
2986: .Nm prime
2987: command is used to generate prime numbers,
2988: or to check numbers for primality.
2989: Results are probabilistic:
2990: they have an exceedingly high likelihood of being correct,
2991: but are not guaranteed.
2992: .Pp
2993: The options are as follows:
2994: .Bl -tag -width Ds
2995: .It Fl bits Ar n
2996: Specify the number of bits in the generated prime number.
2997: Must be used in conjunction with
2998: .Fl generate .
2999: .It Fl checks Ar n
3000: Perform a Miller-Rabin probabilistic primality test with
3001: .Ar n
3002: iterations.
3003: The default is 20.
3004: .It Fl generate
3005: Generate a pseudo-random prime number.
3006: Must be used in conjunction with
3007: .Fl bits .
3008: .It Fl hex
3009: Output in hex format.
3010: .It Fl safe
3011: Generate only
3012: .Qq safe
3013: prime numbers
3014: (i.e. a prime p so that (p-1)/2 is also prime).
3015: .It Ar p
3016: Test if number
3017: .Ar p
3018: is prime.
3019: .El
3020: .Sh RAND
3021: .nr nS 1
3022: .Nm "openssl rand"
3023: .Op Fl base64
3024: .Op Fl hex
3025: .Op Fl out Ar file
3026: .Ar num
3027: .nr nS 0
3028: .Pp
3029: The
3030: .Nm rand
3031: command outputs
3032: .Ar num
3033: pseudo-random bytes.
3034: .Pp
3035: The options are as follows:
3036: .Bl -tag -width Ds
3037: .It Fl base64
3038: Perform
3039: .Em base64
3040: encoding on the output.
3041: .It Fl hex
3042: Specify hexadecimal output.
3043: .It Fl out Ar file
1.63 jmc 3044: The output file to write to,
3045: or standard output if not specified.
1.1 jsing 3046: .El
3047: .Sh REQ
3048: .nr nS 1
3049: .Nm "openssl req"
3050: .Op Fl asn1-kludge
3051: .Op Fl batch
3052: .Op Fl config Ar file
3053: .Op Fl days Ar n
3054: .Op Fl extensions Ar section
3055: .Op Fl in Ar file
1.63 jmc 3056: .Op Fl inform Cm der | pem
1.1 jsing 3057: .Op Fl key Ar keyfile
1.63 jmc 3058: .Op Fl keyform Cm der | pem
1.1 jsing 3059: .Op Fl keyout Ar file
1.28 doug 3060: .Op Fl md4 | md5 | sha1
1.1 jsing 3061: .Op Fl modulus
3062: .Op Fl nameopt Ar option
3063: .Op Fl new
3064: .Op Fl newhdr
3065: .Op Fl newkey Ar arg
3066: .Op Fl no-asn1-kludge
3067: .Op Fl nodes
3068: .Op Fl noout
3069: .Op Fl out Ar file
1.63 jmc 3070: .Op Fl outform Cm der | pem
1.1 jsing 3071: .Op Fl passin Ar arg
3072: .Op Fl passout Ar arg
3073: .Op Fl pubkey
3074: .Op Fl reqexts Ar section
3075: .Op Fl reqopt Ar option
3076: .Op Fl set_serial Ar n
3077: .Op Fl subj Ar arg
3078: .Op Fl subject
3079: .Op Fl text
3080: .Op Fl utf8
3081: .Op Fl verbose
3082: .Op Fl verify
3083: .Op Fl x509
3084: .nr nS 0
3085: .Pp
3086: The
3087: .Nm req
3088: command primarily creates and processes certificate requests
3089: in PKCS#10 format.
3090: It can additionally create self-signed certificates,
3091: for use as root CAs, for example.
3092: .Pp
3093: The options are as follows:
3094: .Bl -tag -width Ds
3095: .It Fl asn1-kludge
1.63 jmc 3096: Produce requests in an invalid format for certain picky CAs.
3097: Very few CAs still require the use of this option.
1.1 jsing 3098: .It Fl batch
3099: Non-interactive mode.
3100: .It Fl config Ar file
1.63 jmc 3101: Specify an alternative configuration file.
1.1 jsing 3102: .It Fl days Ar n
1.63 jmc 3103: Specify the number of days to certify the certificate for.
3104: The default is 30 days.
3105: Used with the
1.1 jsing 3106: .Fl x509
1.63 jmc 3107: option.
1.1 jsing 3108: .It Fl extensions Ar section , Fl reqexts Ar section
1.63 jmc 3109: Specify alternative sections to include certificate
3110: extensions (with
3111: .Fl x509 )
3112: or certificate request extensions,
3113: allowing several different sections to be used in the same configuration file.
1.1 jsing 3114: .It Fl in Ar file
1.63 jmc 3115: The input file to read a request from,
3116: or standard input if not specified.
1.1 jsing 3117: A request is only read if the creation options
3118: .Fl new
3119: and
3120: .Fl newkey
3121: are not specified.
1.63 jmc 3122: .It Fl inform Cm der | pem
3123: The input format.
1.1 jsing 3124: .It Fl key Ar keyfile
1.63 jmc 3125: The file to read the private key from.
1.1 jsing 3126: It also accepts PKCS#8 format private keys for PEM format files.
1.63 jmc 3127: .It Fl keyform Cm der | pem
1.1 jsing 3128: The format of the private key file specified in the
3129: .Fl key
3130: argument.
1.63 jmc 3131: The default is PEM.
1.1 jsing 3132: .It Fl keyout Ar file
1.63 jmc 3133: The file to write the newly created private key to.
3134: If this option is not specified,
3135: the filename present in the configuration file is used.
1.4 sthen 3136: .It Fl md5 | sha1 | sha256
1.63 jmc 3137: The message digest to sign the request with.
1.1 jsing 3138: This overrides the digest algorithm specified in the configuration file.
3139: .Pp
3140: Some public key algorithms may override this choice.
3141: For instance, DSA signatures always use SHA1.
3142: .It Fl modulus
1.63 jmc 3143: Print the value of the modulus of the public key contained in the request.
1.1 jsing 3144: .It Fl nameopt Ar option , Fl reqopt Ar option
1.63 jmc 3145: Determine how the subject or issuer names are displayed.
1.1 jsing 3146: .Ar option
1.63 jmc 3147: can be a single option or multiple options separated by commas.
1.1 jsing 3148: Alternatively, these options may be used more than once to set multiple options.
3149: See the
3150: .Sx X509
3151: section below for details.
3152: .It Fl new
1.63 jmc 3153: Generate a new certificate request.
3154: The user is prompted for the relevant field values.
1.1 jsing 3155: The actual fields prompted for and their maximum and minimum sizes
3156: are specified in the configuration file and any requested extensions.
3157: .Pp
3158: If the
3159: .Fl key
3160: option is not used, it will generate a new RSA private
3161: key using information specified in the configuration file.
3162: .It Fl newhdr
1.63 jmc 3163: Add the word NEW to the PEM file header and footer lines
1.1 jsing 3164: on the outputed request.
1.63 jmc 3165: Some software and CAs need this.
1.1 jsing 3166: .It Fl newkey Ar arg
1.63 jmc 3167: Create a new certificate request and a new private key.
1.1 jsing 3168: The argument takes one of several forms.
1.63 jmc 3169: .Pp
3170: .No rsa : Ns Ar nbits
3171: generates an RSA key
1.1 jsing 3172: .Ar nbits
3173: in size.
3174: If
3175: .Ar nbits
1.63 jmc 3176: is omitted
3177: the default key size is used.
3178: .Pp
3179: .No dsa : Ns Ar file
3180: generates a DSA key using the parameters in
3181: .Ar file .
3182: .Pp
3183: .No param : Ns Ar file
3184: generates a key using the parameters or certificate in
3185: .Ar file .
3186: .Pp
3187: All other algorithms support the form
3188: .Ar algorithm : Ns Ar file ,
1.1 jsing 3189: where file may be an algorithm parameter file,
3190: created by the
3191: .Cm genpkey -genparam
1.14 jmc 3192: command or an X.509 certificate for a key with appropriate algorithm.
1.63 jmc 3193: .Ar file
3194: can be omitted,
3195: in which case any parameters can be specified via the
1.1 jsing 3196: .Fl pkeyopt
3197: option.
3198: .It Fl no-asn1-kludge
1.63 jmc 3199: Reverse the effect of
1.1 jsing 3200: .Fl asn1-kludge .
3201: .It Fl nodes
1.63 jmc 3202: Do not encrypt the private key.
1.1 jsing 3203: .It Fl noout
1.63 jmc 3204: Do not output the encoded version of the request.
1.1 jsing 3205: .It Fl out Ar file
1.63 jmc 3206: The output file to write to,
3207: or standard output if not spceified.
3208: .It Fl outform Cm der | pem
3209: The output format.
1.1 jsing 3210: .It Fl passin Ar arg
3211: The key password source.
3212: .It Fl passout Ar arg
3213: The output file password source.
3214: .It Fl pubkey
1.63 jmc 3215: Output the public key.
1.1 jsing 3216: .It Fl reqopt Ar option
3217: Customise the output format used with
3218: .Fl text .
3219: The
3220: .Ar option
3221: argument can be a single option or multiple options separated by commas.
1.63 jmc 3222: See also the discussion of
1.1 jsing 3223: .Fl certopt
1.63 jmc 3224: in the
1.1 jsing 3225: .Nm x509
3226: command.
3227: .It Fl set_serial Ar n
3228: Serial number to use when outputting a self-signed certificate.
3229: This may be specified as a decimal value or a hex value if preceded by
3230: .Sq 0x .
3231: It is possible to use negative serial numbers but this is not recommended.
3232: .It Fl subj Ar arg
1.63 jmc 3233: Replaces the subject field of an input request
3234: with the specified data and output the modified request.
3235: .Ar arg
3236: must be formatted as /type0=value0/type1=value1/type2=...;
1.1 jsing 3237: characters may be escaped by
3238: .Sq \e
1.63 jmc 3239: (backslash);
1.1 jsing 3240: no spaces are skipped.
3241: .It Fl subject
1.63 jmc 3242: Print the request subject (or certificate subject if
1.1 jsing 3243: .Fl x509
1.63 jmc 3244: is specified).
1.1 jsing 3245: .It Fl text
1.64 jmc 3246: Print the certificate request in plain text.
1.1 jsing 3247: .It Fl utf8
1.63 jmc 3248: Interpret field values as UTF8 strings, not ASCII.
1.1 jsing 3249: .It Fl verbose
3250: Print extra details about the operations being performed.
3251: .It Fl verify
1.63 jmc 3252: Verify the signature on the request.
1.1 jsing 3253: .It Fl x509
1.63 jmc 3254: Output a self-signed certificate instead of a certificate request.
3255: This is typically used to generate a test certificate or a self-signed root CA.
3256: The extensions added to the certificate (if any)
1.1 jsing 3257: are specified in the configuration file.
3258: Unless specified using the
3259: .Fl set_serial
1.63 jmc 3260: option, 0 is used for the serial number.
1.1 jsing 3261: .El
1.63 jmc 3262: .Pp
1.1 jsing 3263: The configuration options are specified in the
1.63 jmc 3264: .Qq req
1.1 jsing 3265: section of the configuration file.
3266: As with all configuration files, if no value is specified in the specific
1.63 jmc 3267: section then the initial unnamed or default section is searched too.
1.1 jsing 3268: .Pp
1.63 jmc 3269: The options available are as follows:
1.1 jsing 3270: .Bl -tag -width "XXXX"
1.63 jmc 3271: .It Cm attributes
3272: The section containing any request attributes: its format
1.1 jsing 3273: is the same as
1.63 jmc 3274: .Cm distinguished_name .
3275: Typically these may contain the challengePassword or unstructuredName types.
3276: They are currently ignored by the
3277: .Nm openssl
1.1 jsing 3278: request signing utilities, but some CAs might want them.
1.63 jmc 3279: .It Cm default_bits
3280: The default key size, in bits.
3281: The default is 2048.
1.1 jsing 3282: It is used if the
3283: .Fl new
1.63 jmc 3284: option is used and can be overridden by using the
1.1 jsing 3285: .Fl newkey
3286: option.
1.63 jmc 3287: .It Cm default_keyfile
3288: The default file to write a private key to,
3289: or standard output if not specified.
3290: It can be overridden by the
1.1 jsing 3291: .Fl keyout
3292: option.
1.63 jmc 3293: .It Cm default_md
3294: The digest algorithm to use.
1.1 jsing 3295: Possible values include
1.63 jmc 3296: .Cm md5 ,
3297: .Cm sha1
1.1 jsing 3298: and
1.63 jmc 3299: .Cm sha256
3300: (the default).
3301: It can be overridden on the command line.
3302: .It Cm distinguished_name
3303: The section containing the distinguished name fields to
1.1 jsing 3304: prompt for when generating a certificate or certificate request.
1.63 jmc 3305: The format is described below.
3306: .It Cm encrypt_key
3307: If set to
3308: .Qq no
3309: and a private key is generated, it is not encrypted.
3310: It is equivalent to the
1.1 jsing 3311: .Fl nodes
1.63 jmc 3312: option.
1.1 jsing 3313: For compatibility,
1.63 jmc 3314: .Cm encrypt_rsa_key
1.1 jsing 3315: is an equivalent option.
1.63 jmc 3316: .It Cm input_password | output_password
3317: The passwords for the input private key file (if present)
3318: and the output private key file (if one will be created).
1.1 jsing 3319: The command line options
3320: .Fl passin
3321: and
3322: .Fl passout
3323: override the configuration file values.
1.63 jmc 3324: .It Cm oid_file
3325: A file containing additional OBJECT IDENTIFIERS.
1.1 jsing 3326: Each line of the file should consist of the numerical form of the
3327: object identifier, followed by whitespace, then the short name followed
3328: by whitespace and finally the long name.
1.63 jmc 3329: .It Cm oid_section
3330: Specify a section in the configuration file containing extra
1.1 jsing 3331: object identifiers.
3332: Each line should consist of the short name of the
3333: object identifier followed by
3334: .Sq =
3335: and the numerical form.
3336: The short and long names are the same when this option is used.
1.63 jmc 3337: .It Cm prompt
3338: If set to
3339: .Qq no ,
3340: it disables prompting of certificate fields
1.1 jsing 3341: and just takes values from the config file directly.
3342: It also changes the expected format of the
1.63 jmc 3343: .Cm distinguished_name
1.1 jsing 3344: and
1.63 jmc 3345: .Cm attributes
1.1 jsing 3346: sections.
1.63 jmc 3347: .It Cm req_extensions
3348: The configuration file section containing a list of
1.1 jsing 3349: extensions to add to the certificate request.
3350: It can be overridden by the
3351: .Fl reqexts
1.63 jmc 3352: option.
3353: .It Cm string_mask
3354: Limit the string types for encoding certain fields.
1.1 jsing 3355: The following values may be used, limiting strings to the indicated types:
3356: .Bl -tag -width "MASK:number"
1.63 jmc 3357: .It Cm utf8only
3358: UTF8String.
1.1 jsing 3359: This is the default, as recommended by PKIX in RFC 2459.
1.63 jmc 3360: .It Cm default
3361: PrintableString, IA5String, T61String, BMPString, UTF8String.
3362: .It Cm pkix
3363: PrintableString, IA5String, BMPString, UTF8String.
3364: Inspired by the PKIX recommendation in RFC 2459 for certificates
3365: generated before 2004, but differs by also permitting IA5String.
3366: .It Cm nombstr
3367: PrintableString, IA5String, T61String, UniversalString.
3368: A workaround for some ancient software that had problems
3369: with the variable-sized BMPString and UTF8String types.
1.1 jsing 3370: .It Cm MASK : Ns Ar number
1.63 jmc 3371: An explicit bitmask of permitted types, where
1.1 jsing 3372: .Ar number
3373: is a C-style hex, decimal, or octal number that's a bit-wise OR of
3374: .Dv B_ASN1_*
3375: values from
3376: .In openssl/asn1.h .
3377: .El
1.63 jmc 3378: .It Cm utf8
3379: If set to
3380: .Qq yes ,
3381: field values are interpreted as UTF8 strings, not ASCII.
3382: .It Cm x509_extensions
3383: The configuration file section containing a list of
1.1 jsing 3384: extensions to add to a certificate generated when the
3385: .Fl x509
3386: switch is used.
3387: It can be overridden by the
3388: .Fl extensions
1.63 jmc 3389: option.
1.1 jsing 3390: .El
1.63 jmc 3391: .Pp
1.1 jsing 3392: There are two separate formats for the distinguished name and attribute
3393: sections.
3394: If the
3395: .Fl prompt
3396: option is set to
1.63 jmc 3397: .Qq no ,
3398: the sections consist of just field names and values,
3399: which allows external programs to generate a template file
3400: with all the field names and values and just pass it to
1.1 jsing 3401: .Nm req .
3402: .Pp
3403: Alternatively if the
3404: .Fl prompt
3405: option is absent or not set to
1.63 jmc 3406: .Qq no ,
1.1 jsing 3407: then the file contains field prompting information.
3408: It consists of lines of the form:
3409: .Bd -unfilled -offset indent
3410: fieldName="prompt"
3411: fieldName_default="default field value"
3412: fieldName_min= 2
3413: fieldName_max= 4
3414: .Ed
3415: .Pp
3416: .Qq fieldName
3417: is the field name being used, for example
1.63 jmc 3418: .Cm commonName
3419: (or CN).
1.1 jsing 3420: The
3421: .Qq prompt
3422: string is used to ask the user to enter the relevant details.
3423: If the user enters nothing, the default value is used;
3424: if no default value is present, the field is omitted.
3425: A field can still be omitted if a default value is present,
3426: if the user just enters the
3427: .Sq \&.
3428: character.
3429: .Pp
3430: The number of characters entered must be between the
1.63 jmc 3431: fieldName_min and fieldName_max limits:
1.1 jsing 3432: there may be additional restrictions based on the field being used
3433: (for example
1.63 jmc 3434: .Cm countryName
1.1 jsing 3435: can only ever be two characters long and must fit in a
1.63 jmc 3436: .Cm PrintableString ) .
1.1 jsing 3437: .Pp
3438: Some fields (such as
1.63 jmc 3439: .Cm organizationName )
1.1 jsing 3440: can be used more than once in a DN.
3441: This presents a problem because configuration files will
3442: not recognize the same name occurring twice.
3443: To avoid this problem, if the
1.63 jmc 3444: .Cm fieldName
1.1 jsing 3445: contains some characters followed by a full stop, they will be ignored.
3446: So, for example, a second
1.63 jmc 3447: .Cm organizationName
1.1 jsing 3448: can be input by calling it
3449: .Qq 1.organizationName .
3450: .Pp
3451: The actual permitted field names are any object identifier short or
3452: long names.
3453: These are compiled into
1.63 jmc 3454: .Nm openssl
1.1 jsing 3455: and include the usual values such as
1.63 jmc 3456: .Cm commonName , countryName , localityName , organizationName ,
3457: .Cm organizationUnitName , stateOrProvinceName .
1.1 jsing 3458: Additionally,
1.63 jmc 3459: .Cm emailAddress
1.1 jsing 3460: is included as well as
1.63 jmc 3461: .Cm name , surname , givenName , initials
1.1 jsing 3462: and
1.63 jmc 3463: .Cm dnQualifier .
1.1 jsing 3464: .Pp
3465: Additional object identifiers can be defined with the
1.63 jmc 3466: .Cm oid_file
1.1 jsing 3467: or
1.63 jmc 3468: .Cm oid_section
1.1 jsing 3469: options in the configuration file.
3470: Any additional fields will be treated as though they were a
1.63 jmc 3471: .Cm DirectoryString .
1.1 jsing 3472: .Sh RSA
3473: .nr nS 1
3474: .Nm "openssl rsa"
1.64 jmc 3475: .Op Fl aes128 | aes192 | aes256 | des | des3
1.1 jsing 3476: .Op Fl check
3477: .Op Fl in Ar file
1.64 jmc 3478: .Op Fl inform Cm der | net | pem
1.1 jsing 3479: .Op Fl modulus
3480: .Op Fl noout
3481: .Op Fl out Ar file
1.64 jmc 3482: .Op Fl outform Cm der | net | pem
1.1 jsing 3483: .Op Fl passin Ar arg
3484: .Op Fl passout Ar arg
3485: .Op Fl pubin
3486: .Op Fl pubout
3487: .Op Fl sgckey
3488: .Op Fl text
3489: .nr nS 0
3490: .Pp
3491: The
3492: .Nm rsa
3493: command processes RSA keys.
3494: They can be converted between various forms and their components printed out.
1.64 jmc 3495: .Nm rsa
3496: uses the traditional
1.1 jsing 3497: .Nm SSLeay
3498: compatible format for private key encryption:
3499: newer applications should use the more secure PKCS#8 format using the
3500: .Nm pkcs8
3501: utility.
3502: .Pp
3503: The options are as follows:
3504: .Bl -tag -width Ds
1.64 jmc 3505: .It Fl aes128 | aes192 | aes256 | des | des3
3506: Encrypt the private key with the AES, DES,
1.1 jsing 3507: or the triple DES ciphers, respectively, before outputting it.
3508: A pass phrase is prompted for.
3509: If none of these options are specified, the key is written in plain text.
3510: This means that using the
3511: .Nm rsa
3512: utility to read in an encrypted key with no encryption option can be used
3513: to remove the pass phrase from a key, or by setting the encryption options
3514: it can be used to add or change the pass phrase.
3515: These options can only be used with PEM format output files.
3516: .It Fl check
1.64 jmc 3517: Check the consistency of an RSA private key.
1.1 jsing 3518: .It Fl in Ar file
1.64 jmc 3519: The input file to read from,
3520: or standard input if not specified.
1.1 jsing 3521: If the key is encrypted, a pass phrase will be prompted for.
1.64 jmc 3522: .It Fl inform Cm der | net | pem
3523: The input format.
1.1 jsing 3524: .It Fl noout
1.64 jmc 3525: Do not output the encoded version of the key.
1.1 jsing 3526: .It Fl modulus
1.64 jmc 3527: Print the value of the modulus of the key.
1.1 jsing 3528: .It Fl out Ar file
1.64 jmc 3529: The output file to write to,
3530: or standard output if not specified.
3531: .It Fl outform Cm der | net | pem
3532: The output format.
1.1 jsing 3533: .It Fl passin Ar arg
3534: The key password source.
3535: .It Fl passout Ar arg
3536: The output file password source.
3537: .It Fl pubin
1.64 jmc 3538: Read in a public key,
3539: not a private key.
1.1 jsing 3540: .It Fl pubout
1.64 jmc 3541: Output a public key,
3542: not a private key.
3543: Automatically set if the input is a public key.
1.1 jsing 3544: .It Fl sgckey
1.64 jmc 3545: Use the modified NET algorithm used with some versions of Microsoft IIS
3546: and SGC keys.
1.1 jsing 3547: .It Fl text
1.64 jmc 3548: Print the public/private key components in plain text.
1.1 jsing 3549: .El
3550: .Sh RSAUTL
3551: .nr nS 1
3552: .Nm "openssl rsautl"
3553: .Op Fl asn1parse
3554: .Op Fl certin
3555: .Op Fl decrypt
3556: .Op Fl encrypt
3557: .Op Fl hexdump
3558: .Op Fl in Ar file
3559: .Op Fl inkey Ar file
1.65 jmc 3560: .Op Fl keyform Cm der | pem
1.1 jsing 3561: .Op Fl oaep | pkcs | raw | ssl
3562: .Op Fl out Ar file
3563: .Op Fl pubin
3564: .Op Fl sign
3565: .Op Fl verify
3566: .nr nS 0
3567: .Pp
3568: The
3569: .Nm rsautl
3570: command can be used to sign, verify, encrypt and decrypt
3571: data using the RSA algorithm.
3572: .Pp
3573: The options are as follows:
3574: .Bl -tag -width Ds
3575: .It Fl asn1parse
3576: Asn1parse the output data; this is useful when combined with the
3577: .Fl verify
3578: option.
3579: .It Fl certin
3580: The input is a certificate containing an RSA public key.
3581: .It Fl decrypt
3582: Decrypt the input data using an RSA private key.
3583: .It Fl encrypt
3584: Encrypt the input data using an RSA public key.
3585: .It Fl hexdump
3586: Hex dump the output data.
3587: .It Fl in Ar file
1.65 jmc 3588: The input to read from,
3589: or standard input if not specified.
1.1 jsing 3590: .It Fl inkey Ar file
1.65 jmc 3591: The input key file; by default an RSA private key.
3592: .It Fl keyform Cm der | pem
3593: The private ket format.
3594: The default is
3595: .Cm pem .
1.1 jsing 3596: .It Fl oaep | pkcs | raw | ssl
3597: The padding to use:
1.65 jmc 3598: PKCS#1 OAEP, PKCS#1 v1.5 (the default), or no padding, respectively.
1.1 jsing 3599: For signatures, only
3600: .Fl pkcs
3601: and
3602: .Fl raw
3603: can be used.
3604: .It Fl out Ar file
1.65 jmc 3605: The output file to write to,
3606: or standard output if not specified.
1.1 jsing 3607: .It Fl pubin
3608: The input file is an RSA public key.
3609: .It Fl sign
3610: Sign the input data and output the signed result.
3611: This requires an RSA private key.
3612: .It Fl verify
3613: Verify the input data and output the recovered data.
3614: .El
3615: .Sh S_CLIENT
3616: .nr nS 1
3617: .Nm "openssl s_client"
3618: .Op Fl 4 | 6
3619: .Op Fl bugs
3620: .Op Fl CAfile Ar file
3621: .Op Fl CApath Ar directory
3622: .Op Fl cert Ar file
3623: .Op Fl check_ss_sig
3624: .Op Fl cipher Ar cipherlist
1.66 jmc 3625: .Op Fl connect Ar host Ns Op : Ns Ar port
1.1 jsing 3626: .Op Fl crl_check
3627: .Op Fl crl_check_all
3628: .Op Fl crlf
3629: .Op Fl debug
3630: .Op Fl extended_crl
3631: .Op Fl ign_eof
3632: .Op Fl ignore_critical
3633: .Op Fl issuer_checks
3634: .Op Fl key Ar keyfile
3635: .Op Fl msg
3636: .Op Fl nbio
3637: .Op Fl nbio_test
3638: .Op Fl no_ticket
3639: .Op Fl no_tls1
1.6 guenther 3640: .Op Fl no_tls1_1
3641: .Op Fl no_tls1_2
1.1 jsing 3642: .Op Fl pause
3643: .Op Fl policy_check
3644: .Op Fl prexit
1.11 bluhm 3645: .Op Fl proxy Ar host : Ns Ar port
1.1 jsing 3646: .Op Fl psk Ar key
3647: .Op Fl psk_identity Ar identity
3648: .Op Fl quiet
3649: .Op Fl reconnect
1.5 jsing 3650: .Op Fl servername Ar name
1.1 jsing 3651: .Op Fl showcerts
3652: .Op Fl starttls Ar protocol
3653: .Op Fl state
3654: .Op Fl tls1
1.31 jmc 3655: .Op Fl tls1_1
3656: .Op Fl tls1_2
1.1 jsing 3657: .Op Fl tlsextdebug
3658: .Op Fl verify Ar depth
3659: .Op Fl x509_strict
1.19 landry 3660: .Op Fl xmpphost Ar host
1.1 jsing 3661: .nr nS 0
3662: .Pp
3663: The
3664: .Nm s_client
3665: command implements a generic SSL/TLS client which connects
3666: to a remote host using SSL/TLS.
1.66 jmc 3667: .Pp
3668: If a connection is established with an SSL server, any data received
3669: from the server is displayed and any key presses will be sent to the
3670: server.
3671: When used interactively (which means neither
3672: .Fl quiet
3673: nor
3674: .Fl ign_eof
3675: have been given), the session will be renegotiated if the line begins with an
3676: .Cm R ;
3677: if the line begins with a
3678: .Cm Q
3679: or if end of file is reached, the connection will be closed down.
1.1 jsing 3680: .Pp
3681: The options are as follows:
3682: .Bl -tag -width Ds
3683: .It Fl 4
1.66 jmc 3684: Attempt connections using IPv4 only.
1.1 jsing 3685: .It Fl 6
1.66 jmc 3686: Attempt connections using IPv6 only.
1.1 jsing 3687: .It Fl bugs
1.66 jmc 3688: Enable various workarounds for buggy implementations.
1.1 jsing 3689: .It Fl CAfile Ar file
3690: A
3691: .Ar file
3692: containing trusted certificates to use during server authentication
3693: and to use when attempting to build the client certificate chain.
3694: .It Fl CApath Ar directory
3695: The
3696: .Ar directory
3697: to use for server certificate verification.
3698: This directory must be in
3699: .Qq hash format ;
3700: see
3701: .Fl verify
3702: for more information.
3703: These are also used when building the client certificate chain.
3704: .It Fl cert Ar file
3705: The certificate to use, if one is requested by the server.
3706: The default is not to use a certificate.
3707: .It Xo
3708: .Fl check_ss_sig ,
3709: .Fl crl_check ,
3710: .Fl crl_check_all ,
3711: .Fl extended_crl ,
3712: .Fl ignore_critical ,
3713: .Fl issuer_checks ,
3714: .Fl policy_check ,
3715: .Fl x509_strict
3716: .Xc
3717: Set various certificate chain validation options.
3718: See the
1.66 jmc 3719: .Nm verify
1.1 jsing 3720: command for details.
3721: .It Fl cipher Ar cipherlist
1.66 jmc 3722: Modify the cipher list sent by the client.
1.1 jsing 3723: Although the server determines which cipher suite is used, it should take
3724: the first supported cipher in the list sent by the client.
3725: See the
1.66 jmc 3726: .Nm ciphers
3727: command for more information.
3728: .It Fl connect Ar host Ns Op : Ns Ar port
3729: The
1.1 jsing 3730: .Ar host
1.66 jmc 3731: and
1.1 jsing 3732: .Ar port
3733: to connect to.
3734: If not specified, an attempt is made to connect to the local host
3735: on port 4433.
3736: Alternatively, the host and port pair may be separated using a forward-slash
1.66 jmc 3737: character,
3738: which is useful for numeric IPv6 addresses.
1.1 jsing 3739: .It Fl crlf
1.66 jmc 3740: Translate a line feed from the terminal into CR+LF,
3741: as required by some servers.
1.1 jsing 3742: .It Fl debug
1.66 jmc 3743: Print extensive debugging information, including a hex dump of all traffic.
1.1 jsing 3744: .It Fl ign_eof
1.66 jmc 3745: Inhibit shutting down the connection when end of file is reached in the input.
1.1 jsing 3746: .It Fl key Ar keyfile
3747: The private key to use.
3748: If not specified, the certificate file will be used.
3749: .It Fl msg
3750: Show all protocol messages with hex dump.
3751: .It Fl nbio
1.66 jmc 3752: Turn on non-blocking I/O.
1.1 jsing 3753: .It Fl nbio_test
1.66 jmc 3754: Test non-blocking I/O.
1.31 jmc 3755: .It Fl no_tls1 | no_tls1_1 | no_tls1_2
1.66 jmc 3756: Disable the use of TLS1.0, 1.1, and 1.2, respectively.
1.1 jsing 3757: .It Fl no_ticket
3758: Disable RFC 4507 session ticket support.
3759: .It Fl pause
1.66 jmc 3760: Pause 1 second between each read and write call.
1.1 jsing 3761: .It Fl prexit
3762: Print session information when the program exits.
3763: This will always attempt
3764: to print out information even if the connection fails.
3765: Normally, information will only be printed out once if the connection succeeds.
3766: This option is useful because the cipher in use may be renegotiated
3767: or the connection may fail because a client certificate is required or is
3768: requested only after an attempt is made to access a certain URL.
1.66 jmc 3769: Note that the output produced by this option is not always accurate
3770: because a connection might never have been established.
1.11 bluhm 3771: .It Fl proxy Ar host : Ns Ar port
3772: Use the HTTP proxy at
3773: .Ar host
3774: and
3775: .Ar port .
3776: The connection to the proxy is done in cleartext and the
3777: .Fl connect
3778: argument is given to the proxy.
3779: If not specified, localhost is used as final destination.
3780: After that, switch the connection through the proxy to the destination
3781: to TLS.
1.1 jsing 3782: .It Fl psk Ar key
3783: Use the PSK key
3784: .Ar key
3785: when using a PSK cipher suite.
3786: The key is given as a hexadecimal number without the leading 0x,
3787: for example -psk 1a2b3c4d.
3788: .It Fl psk_identity Ar identity
1.66 jmc 3789: Use the PSK
1.1 jsing 3790: .Ar identity
3791: when using a PSK cipher suite.
3792: .It Fl quiet
3793: Inhibit printing of session and certificate information.
3794: This implicitly turns on
3795: .Fl ign_eof
3796: as well.
3797: .It Fl reconnect
1.66 jmc 3798: Reconnect to the same server 5 times using the same session ID; this can
1.1 jsing 3799: be used as a test that session caching is working.
1.5 jsing 3800: .It Fl servername Ar name
3801: Include the TLS Server Name Indication (SNI) extension in the ClientHello
3802: message, using the specified server
3803: .Ar name .
1.1 jsing 3804: .It Fl showcerts
3805: Display the whole server certificate chain: normally only the server
3806: certificate itself is displayed.
3807: .It Fl starttls Ar protocol
1.66 jmc 3808: Send the protocol-specific messages to switch to TLS for communication.
1.1 jsing 3809: .Ar protocol
3810: is a keyword for the intended protocol.
3811: Currently, the supported keywords are
3812: .Qq ftp ,
3813: .Qq imap ,
3814: .Qq smtp ,
3815: .Qq pop3 ,
3816: and
3817: .Qq xmpp .
3818: .It Fl state
1.66 jmc 3819: Print the SSL session states.
1.31 jmc 3820: .It Fl tls1 | tls1_1 | tls1_2
3821: Permit only TLS1.0, 1.1, or 1.2, respectively.
1.1 jsing 3822: .It Fl tlsextdebug
1.66 jmc 3823: Print a hex dump of any TLS extensions received from the server.
1.1 jsing 3824: .It Fl verify Ar depth
1.66 jmc 3825: Turn on server certificate verification,
3826: with a maximum length of
3827: .Ar depth .
1.1 jsing 3828: Currently the verify operation continues after errors so all the problems
3829: with a certificate chain can be seen.
3830: As a side effect the connection will never fail due to a server
3831: certificate verify failure.
1.19 landry 3832: .It Fl xmpphost Ar hostname
1.66 jmc 3833: When used with
1.19 landry 3834: .Fl starttls Ar xmpp ,
1.66 jmc 3835: specify the host for the "to" attribute of the stream element.
1.19 landry 3836: If this option is not specified then the host specified with
3837: .Fl connect
3838: will be used.
1.1 jsing 3839: .El
3840: .Sh S_SERVER
3841: .nr nS 1
3842: .Nm "openssl s_server"
3843: .Op Fl accept Ar port
3844: .Op Fl bugs
3845: .Op Fl CAfile Ar file
3846: .Op Fl CApath Ar directory
3847: .Op Fl cert Ar file
3848: .Op Fl cipher Ar cipherlist
3849: .Op Fl context Ar id
3850: .Op Fl crl_check
3851: .Op Fl crl_check_all
3852: .Op Fl crlf
3853: .Op Fl dcert Ar file
3854: .Op Fl debug
3855: .Op Fl dhparam Ar file
3856: .Op Fl dkey Ar file
3857: .Op Fl hack
3858: .Op Fl HTTP
3859: .Op Fl id_prefix Ar arg
3860: .Op Fl key Ar keyfile
3861: .Op Fl msg
3862: .Op Fl nbio
3863: .Op Fl nbio_test
3864: .Op Fl no_dhe
3865: .Op Fl no_tls1
1.6 guenther 3866: .Op Fl no_tls1_1
3867: .Op Fl no_tls1_2
1.1 jsing 3868: .Op Fl no_tmp_rsa
3869: .Op Fl nocert
3870: .Op Fl psk Ar key
3871: .Op Fl psk_hint Ar hint
3872: .Op Fl quiet
3873: .Op Fl serverpref
3874: .Op Fl state
3875: .Op Fl tls1
1.31 jmc 3876: .Op Fl tls1_1
3877: .Op Fl tls1_2
1.1 jsing 3878: .Op Fl Verify Ar depth
3879: .Op Fl verify Ar depth
3880: .Op Fl WWW
3881: .Op Fl www
3882: .nr nS 0
3883: .Pp
3884: The
3885: .Nm s_server
3886: command implements a generic SSL/TLS server which listens
3887: for connections on a given port using SSL/TLS.
3888: .Pp
1.67 jmc 3889: If a connection request is established with a client and neither the
3890: .Fl www
3891: nor the
3892: .Fl WWW
3893: option has been used, then any data received
3894: from the client is displayed and any key presses are sent to the client.
3895: Certain single letter commands perform special operations:
3896: .Pp
3897: .Bl -tag -width "XXXX" -compact
3898: .It Ic P
3899: Send plain text, which should cause the client to disconnect.
3900: .It Ic Q
3901: End the current SSL connection and exit.
3902: .It Ic q
3903: End the current SSL connection, but still accept new connections.
3904: .It Ic R
3905: Renegotiate the SSL session and request a client certificate.
3906: .It Ic r
3907: Renegotiate the SSL session.
3908: .It Ic S
3909: Print out some session cache status information.
3910: .El
3911: .Pp
1.1 jsing 3912: The options are as follows:
3913: .Bl -tag -width Ds
3914: .It Fl accept Ar port
1.67 jmc 3915: Listen on TCP
1.1 jsing 3916: .Ar port
1.67 jmc 3917: for connections.
3918: The default is port 4433.
1.1 jsing 3919: .It Fl bugs
1.67 jmc 3920: Enable various workarounds for buggy implementations.
1.1 jsing 3921: .It Fl CAfile Ar file
1.67 jmc 3922: A
3923: .Ar file
3924: containing trusted certificates to use during client authentication
1.1 jsing 3925: and to use when attempting to build the server certificate chain.
3926: The list is also used in the list of acceptable client CAs passed to the
3927: client when a certificate is requested.
3928: .It Fl CApath Ar directory
3929: The
3930: .Ar directory
3931: to use for client certificate verification.
3932: This directory must be in
3933: .Qq hash format ;
3934: see
3935: .Fl verify
3936: for more information.
3937: These are also used when building the server certificate chain.
3938: .It Fl cert Ar file
1.67 jmc 3939: The certificate to use: most server's cipher suites require the use of a
3940: certificate and some require a certificate with a certain public key type.
3941: For example, the DSS cipher suites require a certificate containing a DSS
3942: (DSA) key.
1.1 jsing 3943: If not specified, the file
3944: .Pa server.pem
3945: will be used.
3946: .It Fl cipher Ar cipherlist
1.67 jmc 3947: Modify the cipher list used by the server.
1.1 jsing 3948: This allows the cipher list used by the server to be modified.
3949: When the client sends a list of supported ciphers, the first client cipher
3950: also included in the server list is used.
3951: Because the client specifies the preference order, the order of the server
3952: cipherlist is irrelevant.
3953: See the
1.67 jmc 3954: .Nm ciphers
3955: command for more information.
1.1 jsing 3956: .It Fl context Ar id
1.67 jmc 3957: Set the SSL context ID.
1.1 jsing 3958: It can be given any string value.
3959: .It Fl crl_check , crl_check_all
3960: Check the peer certificate has not been revoked by its CA.
3961: The CRLs are appended to the certificate file.
3962: .Fl crl_check_all
1.67 jmc 3963: checks all CRLs of all CAs in the chain.
1.1 jsing 3964: .It Fl crlf
1.67 jmc 3965: Translate a line feed from the terminal into CR+LF.
1.1 jsing 3966: .It Fl dcert Ar file , Fl dkey Ar file
3967: Specify an additional certificate and private key; these behave in the
3968: same manner as the
3969: .Fl cert
3970: and
3971: .Fl key
3972: options except there is no default if they are not specified
1.67 jmc 3973: (no additional certificate or key is used).
1.1 jsing 3974: By using RSA and DSS certificates and keys,
3975: a server can support clients which only support RSA or DSS cipher suites
3976: by using an appropriate certificate.
3977: .It Fl debug
1.67 jmc 3978: Print extensive debugging information, including a hex dump of all traffic.
1.1 jsing 3979: .It Fl dhparam Ar file
3980: The DH parameter file to use.
3981: The ephemeral DH cipher suites generate keys
3982: using a set of DH parameters.
3983: If not specified, an attempt is made to
3984: load the parameters from the server certificate file.
3985: If this fails, a static set of parameters hard coded into the
3986: .Nm s_server
3987: program will be used.
3988: .It Fl hack
1.67 jmc 3989: Enables a further workaround for some early Netscape SSL code.
1.1 jsing 3990: .It Fl HTTP
1.67 jmc 3991: Emulate a simple web server.
3992: Pages are resolved relative to the current directory.
3993: For example if the URL
1.1 jsing 3994: .Pa https://myhost/page.html
3995: is requested, the file
3996: .Pa ./page.html
3997: will be loaded.
3998: The files loaded are assumed to contain a complete and correct HTTP
3999: response (lines that are part of the HTTP response line and headers
4000: must end with CRLF).
4001: .It Fl id_prefix Ar arg
4002: Generate SSL/TLS session IDs prefixed by
4003: .Ar arg .
4004: This is mostly useful for testing any SSL/TLS code
1.67 jmc 4005: (e.g. proxies)
1.1 jsing 4006: that wish to deal with multiple servers, when each of which might be
4007: generating a unique range of session IDs
1.67 jmc 4008: (e.g. with a certain prefix).
1.1 jsing 4009: .It Fl key Ar keyfile
4010: The private key to use.
4011: If not specified, the certificate file will be used.
4012: .It Fl msg
4013: Show all protocol messages with hex dump.
4014: .It Fl nbio
1.67 jmc 4015: Turn on non-blocking I/O.
1.1 jsing 4016: .It Fl nbio_test
1.67 jmc 4017: Test non-blocking I/O.
1.1 jsing 4018: .It Fl no_dhe
1.67 jmc 4019: Disable ephemeral DH cipher suites.
1.31 jmc 4020: .It Fl no_tls1 | no_tls1_1 | no_tls1_2
1.67 jmc 4021: Disable the use of TLS1.0, 1.1, and 1.2, respectively.
1.1 jsing 4022: .It Fl no_tmp_rsa
1.67 jmc 4023: Disable temporary RSA key generation.
1.1 jsing 4024: .It Fl nocert
1.67 jmc 4025: Do not use a certificate.
1.1 jsing 4026: This restricts the cipher suites available to the anonymous ones
1.67 jmc 4027: (currently just anonymous DH).
1.1 jsing 4028: .It Fl psk Ar key
4029: Use the PSK key
4030: .Ar key
4031: when using a PSK cipher suite.
4032: The key is given as a hexadecimal number without the leading 0x,
4033: for example -psk 1a2b3c4d.
4034: .It Fl psk_hint Ar hint
4035: Use the PSK identity hint
4036: .Ar hint
4037: when using a PSK cipher suite.
4038: .It Fl quiet
4039: Inhibit printing of session and certificate information.
4040: .It Fl serverpref
4041: Use server's cipher preferences.
4042: .It Fl state
1.67 jmc 4043: Print the SSL session states.
1.31 jmc 4044: .It Fl tls1 | tls1_1 | tls1_2
4045: Permit only TLS1.0, 1.1, or 1.2, respectively.
1.1 jsing 4046: .It Fl WWW
1.67 jmc 4047: Emulate a simple web server.
4048: Pages are resolved relative to the current directory.
4049: For example if the URL
1.1 jsing 4050: .Pa https://myhost/page.html
4051: is requested, the file
4052: .Pa ./page.html
4053: will be loaded.
4054: .It Fl www
1.67 jmc 4055: Send a status message to the client when it connects,
4056: including information about the ciphers used and various session parameters.
1.1 jsing 4057: The output is in HTML format so this option will normally be used with a
4058: web browser.
4059: .It Fl Verify Ar depth , Fl verify Ar depth
1.67 jmc 4060: Request a certificate chain from the client,
4061: with a maximum length of
4062: .Ar depth .
4063: With
4064: .Fl Verify ,
4065: the client must supply a certificate or an error occurs;
4066: with
4067: .Fl verify ,
4068: a certificate is requested but the client does not have to send one.
1.1 jsing 4069: .El
4070: .Sh S_TIME
4071: .nr nS 1
4072: .Nm "openssl s_time"
4073: .Op Fl bugs
4074: .Op Fl CAfile Ar file
4075: .Op Fl CApath Ar directory
4076: .Op Fl cert Ar file
4077: .Op Fl cipher Ar cipherlist
1.68 jmc 4078: .Op Fl connect Ar host Ns Op : Ns Ar port
1.1 jsing 4079: .Op Fl key Ar keyfile
4080: .Op Fl nbio
4081: .Op Fl new
1.20 lteo 4082: .Op Fl no_shutdown
1.1 jsing 4083: .Op Fl reuse
4084: .Op Fl time Ar seconds
4085: .Op Fl verify Ar depth
4086: .Op Fl www Ar page
4087: .nr nS 0
4088: .Pp
4089: The
1.68 jmc 4090: .Nm s_time
1.1 jsing 4091: command implements a generic SSL/TLS client which connects to a
4092: remote host using SSL/TLS.
4093: It can request a page from the server and includes
4094: the time to transfer the payload data in its timing measurements.
4095: It measures the number of connections within a given timeframe,
4096: the amount of data transferred
4097: .Pq if any ,
4098: and calculates the average time spent for one connection.
4099: .Pp
4100: The options are as follows:
4101: .Bl -tag -width Ds
4102: .It Fl bugs
1.68 jmc 4103: Enable various workarounds for buggy implementations.
1.1 jsing 4104: .It Fl CAfile Ar file
1.68 jmc 4105: A
4106: .Ar file
4107: containing trusted certificates to use during server authentication
1.1 jsing 4108: and to use when attempting to build the client certificate chain.
4109: .It Fl CApath Ar directory
4110: The directory to use for server certificate verification.
4111: This directory must be in
4112: .Qq hash format ;
4113: see
4114: .Nm verify
4115: for more information.
4116: These are also used when building the client certificate chain.
4117: .It Fl cert Ar file
4118: The certificate to use, if one is requested by the server.
4119: The default is not to use a certificate.
4120: .It Fl cipher Ar cipherlist
1.68 jmc 4121: Modify the cipher list sent by the client.
1.1 jsing 4122: Although the server determines which cipher suite is used,
4123: it should take the first supported cipher in the list sent by the client.
4124: See the
4125: .Nm ciphers
4126: command for more information.
1.68 jmc 4127: .It Fl connect Ar host Ns Op : Ns Ar port
4128: The host and port to connect to.
1.1 jsing 4129: .It Fl key Ar keyfile
4130: The private key to use.
4131: If not specified, the certificate file will be used.
4132: .It Fl nbio
1.68 jmc 4133: Turn on non-blocking I/O.
1.1 jsing 4134: .It Fl new
1.68 jmc 4135: Perform the timing test using a new session ID for each connection.
1.1 jsing 4136: If neither
4137: .Fl new
4138: nor
4139: .Fl reuse
4140: are specified,
4141: they are both on by default and executed in sequence.
1.20 lteo 4142: .It Fl no_shutdown
1.21 jmc 4143: Shut down the connection without sending a
1.68 jmc 4144: .Qq close notify
1.20 lteo 4145: shutdown alert to the server.
1.1 jsing 4146: .It Fl reuse
1.68 jmc 4147: Perform the timing test using the same session ID for each connection.
1.1 jsing 4148: If neither
4149: .Fl new
4150: nor
4151: .Fl reuse
4152: are specified,
4153: they are both on by default and executed in sequence.
4154: .It Fl time Ar seconds
1.68 jmc 4155: Limit
1.1 jsing 4156: .Nm s_time
1.68 jmc 4157: benchmarks to the number of
4158: .Ar seconds .
1.1 jsing 4159: The default is 30 seconds.
4160: .It Fl verify Ar depth
1.68 jmc 4161: Turn on server certificate verification,
4162: with a maximum length of
4163: .Ar depth .
1.1 jsing 4164: Currently the verify operation continues after errors, so all the problems
4165: with a certificate chain can be seen.
4166: As a side effect,
4167: the connection will never fail due to a server certificate verify failure.
4168: .It Fl www Ar page
1.68 jmc 4169: The page to GET from the server.
1.1 jsing 4170: A value of
4171: .Sq /
4172: gets the index.htm[l] page.
4173: If this parameter is not specified,
4174: .Nm s_time
4175: will only perform the handshake to establish SSL connections
4176: but not transfer any payload data.
4177: .El
4178: .Sh SESS_ID
4179: .nr nS 1
4180: .Nm "openssl sess_id"
4181: .Op Fl cert
4182: .Op Fl context Ar ID
4183: .Op Fl in Ar file
1.69 ! jmc 4184: .Op Fl inform Cm der | pem
1.1 jsing 4185: .Op Fl noout
4186: .Op Fl out Ar file
1.69 ! jmc 4187: .Op Fl outform Cm der | pem
1.1 jsing 4188: .Op Fl text
4189: .nr nS 0
4190: .Pp
4191: The
4192: .Nm sess_id
4193: program processes the encoded version of the SSL session structure and
4194: optionally prints out SSL session details
1.69 ! jmc 4195: (for example the SSL session master key)
1.1 jsing 4196: in human readable format.
4197: .Pp
4198: The options are as follows:
4199: .Bl -tag -width Ds
4200: .It Fl cert
4201: If a certificate is present in the session,
4202: it will be output using this option;
4203: if the
4204: .Fl text
4205: option is also present, then it will be printed out in text form.
4206: .It Fl context Ar ID
1.69 ! jmc 4207: Set the session
1.1 jsing 4208: .Ar ID .
1.69 ! jmc 4209: The ID can be any string of characters.
1.1 jsing 4210: .It Fl in Ar file
1.69 ! jmc 4211: The input file to read from,
! 4212: or standard input if not specified.
! 4213: .It Fl inform Cm der | pem
! 4214: The input format.
! 4215: .Cm der
! 4216: uses an ASN1 DER-encoded format containing session details.
1.1 jsing 4217: The precise format can vary from one version to the next.
1.69 ! jmc 4218: .Cm pem
! 4219: is the default format: it consists of the DER
1.1 jsing 4220: format base64-encoded with additional header and footer lines.
4221: .It Fl noout
1.69 ! jmc 4222: Do not output the encoded version of the session.
1.1 jsing 4223: .It Fl out Ar file
1.69 ! jmc 4224: The output file to write to,
! 4225: or standard output if not specified.
! 4226: .It Fl outform Cm der | pem
! 4227: The output format.
1.1 jsing 4228: .It Fl text
1.69 ! jmc 4229: Print the various public or private key components in plain text,
! 4230: in addition to the encoded version.
1.1 jsing 4231: .El
4232: .Pp
1.69 ! jmc 4233: The output of
! 4234: .Nm sess_id
! 4235: is composed as follows:
1.1 jsing 4236: .Pp
1.69 ! jmc 4237: .Bl -tag -width "Verify return code " -offset 3n -compact
! 4238: .It Protocol
! 4239: The protocol in use.
! 4240: .It Cipher
! 4241: The actual raw SSL or TLS cipher code.
! 4242: .It Session-ID
! 4243: The SSL session ID, in hex format.
! 4244: .It Session-ID-ctx
! 4245: The session ID context, in hex format.
! 4246: .It Master-Key
! 4247: The SSL session master key.
! 4248: .It Key-Arg
1.1 jsing 4249: The key argument; this is only used in SSL v2.
1.69 ! jmc 4250: .It Start Time
! 4251: The session start time.
1.1 jsing 4252: .Ux
4253: format.
1.69 ! jmc 4254: .It Timeout
! 4255: The timeout, in seconds.
! 4256: .It Verify return code
! 4257: The return code when a certificate is verified.
1.1 jsing 4258: .El
4259: .Pp
4260: Since the SSL session output contains the master key, it is possible to read
4261: the contents of an encrypted session using this information.
4262: Therefore appropriate security precautions
4263: should be taken if the information is being output by a
4264: .Qq real
4265: application.
4266: This is, however, strongly discouraged and should only be used for
4267: debugging purposes.
4268: .\"
4269: .\" SMIME
4270: .\"
4271: .Sh SMIME
4272: .nr nS 1
4273: .Nm "openssl smime"
4274: .Bk -words
4275: .Oo
4276: .Fl aes128 | aes192 | aes256 | des |
4277: .Fl des3 | rc2-40 | rc2-64 | rc2-128
4278: .Oc
4279: .Op Fl binary
4280: .Op Fl CAfile Ar file
4281: .Op Fl CApath Ar directory
4282: .Op Fl certfile Ar file
4283: .Op Fl check_ss_sig
4284: .Op Fl content Ar file
4285: .Op Fl crl_check
4286: .Op Fl crl_check_all
4287: .Op Fl decrypt
4288: .Op Fl encrypt
4289: .Op Fl extended_crl
4290: .Op Fl from Ar addr
4291: .Op Fl ignore_critical
4292: .Op Fl in Ar file
4293: .Op Fl indef
4294: .Op Fl inform Ar DER | PEM | SMIME
4295: .Op Fl inkey Ar file
4296: .Op Fl issuer_checks
1.22 bcook 4297: .Op Fl keyform Ar PEM
1.1 jsing 4298: .Op Fl md Ar digest
4299: .Op Fl noattr
4300: .Op Fl nocerts
4301: .Op Fl nochain
4302: .Op Fl nodetach
4303: .Op Fl noindef
4304: .Op Fl nointern
4305: .Op Fl nosigs
4306: .Op Fl noverify
4307: .Op Fl out Ar file
4308: .Op Fl outform Ar DER | PEM | SMIME
4309: .Op Fl passin Ar arg
4310: .Op Fl pk7out
4311: .Op Fl policy_check
4312: .Op Fl recip Ar file
4313: .Op Fl resign
4314: .Op Fl sign
4315: .Op Fl signer Ar file
4316: .Op Fl stream
4317: .Op Fl subject Ar s
4318: .Op Fl text
4319: .Op Fl to Ar addr
4320: .Op Fl verify
4321: .Op Fl x509_strict
4322: .Op Ar cert.pem ...
4323: .Ek
4324: .nr nS 0
4325: .Pp
4326: The
4327: .Nm smime
4328: command handles
4329: .Em S/MIME
4330: mail.
4331: It can encrypt, decrypt, sign, and verify
4332: .Em S/MIME
4333: messages.
4334: .Pp
4335: There are six operation options that set the type of operation to be performed.
4336: The meaning of the other options varies according to the operation type.
4337: .Pp
4338: The six operation options are as follows:
4339: .Bl -tag -width "XXXX"
4340: .It Fl decrypt
4341: Decrypt mail using the supplied certificate and private key.
4342: Expects an encrypted mail message in
4343: .Em MIME
4344: format for the input file.
4345: The decrypted mail is written to the output file.
4346: .It Fl encrypt
4347: Encrypt mail for the given recipient certificates.
4348: Input file is the message to be encrypted.
4349: The output file is the encrypted mail in
4350: .Em MIME
4351: format.
4352: .It Fl pk7out
4353: Takes an input message and writes out a PEM-encoded PKCS#7 structure.
4354: .It Fl resign
4355: Resign a message: take an existing message and one or more new signers.
4356: .It Fl sign
4357: Sign mail using the supplied certificate and private key.
4358: Input file is the message to be signed.
4359: The signed message in
4360: .Em MIME
4361: format is written to the output file.
4362: .It Fl verify
4363: Verify signed mail.
4364: Expects a signed mail message on input and outputs the signed data.
4365: Both clear text and opaque signing is supported.
4366: .El
4367: .Pp
1.14 jmc 4368: The remaining options are as follows:
1.1 jsing 4369: .Bl -tag -width "XXXX"
4370: .It Xo
4371: .Fl aes128 | aes192 | aes256 | des |
4372: .Fl des3 | rc2-40 | rc2-64 | rc2-128
4373: .Xc
4374: The encryption algorithm to use.
4375: 128-, 192-, or 256-bit AES,
4376: DES
4377: .Pq 56 bits ,
4378: triple DES
4379: .Pq 168 bits ,
4380: or 40-, 64-, or 128-bit RC2, respectively;
4381: if not specified, 40-bit RC2 is
4382: used.
4383: Only used with
4384: .Fl encrypt .
4385: .It Fl binary
4386: Normally, the input message is converted to
4387: .Qq canonical
4388: format which is effectively using CR and LF as end of line \-
4389: as required by the
4390: .Em S/MIME
4391: specification.
4392: When this option is present no translation occurs.
4393: This is useful when handling binary data which may not be in
4394: .Em MIME
4395: format.
4396: .It Fl CAfile Ar file
4397: A
4398: .Ar file
4399: containing trusted CA certificates; only used with
4400: .Fl verify .
4401: .It Fl CApath Ar directory
4402: A
4403: .Ar directory
4404: containing trusted CA certificates; only used with
4405: .Fl verify .
4406: This directory must be a standard certificate directory:
4407: that is, a hash of each subject name (using
4408: .Nm x509 -hash )
4409: should be linked to each certificate.
4410: .It Ar cert.pem ...
4411: One or more certificates of message recipients: used when encrypting
4412: a message.
4413: .It Fl certfile Ar file
4414: Allows additional certificates to be specified.
4415: When signing, these will be included with the message.
4416: When verifying, these will be searched for the signers' certificates.
4417: The certificates should be in PEM format.
4418: .It Xo
4419: .Fl check_ss_sig ,
4420: .Fl crl_check ,
4421: .Fl crl_check_all ,
4422: .Fl extended_crl ,
4423: .Fl ignore_critical ,
4424: .Fl issuer_checks ,
4425: .Fl policy_check ,
4426: .Fl x509_strict
4427: .Xc
4428: Set various certificate chain validation options.
4429: See the
4430: .Nm VERIFY
4431: command for details.
4432: .It Fl content Ar file
4433: This specifies a file containing the detached content.
4434: This is only useful with the
4435: .Fl verify
4436: command.
4437: This is only usable if the PKCS#7 structure is using the detached
4438: signature form where the content is not included.
4439: This option will override any content if the input format is
4440: .Em S/MIME
4441: and it uses the multipart/signed
4442: .Em MIME
4443: content type.
4444: .It Xo
4445: .Fl from Ar addr ,
4446: .Fl subject Ar s ,
4447: .Fl to Ar addr
4448: .Xc
4449: The relevant mail headers.
4450: These are included outside the signed
4451: portion of a message so they may be included manually.
4452: When signing, many
4453: .Em S/MIME
4454: mail clients check that the signer's certificate email
4455: address matches the From: address.
4456: .It Fl in Ar file
4457: The input message to be encrypted or signed or the
4458: .Em MIME
4459: message to
4460: be decrypted or verified.
4461: .It Fl indef
4462: Enable streaming I/O for encoding operations.
4463: This permits single pass processing of data without
4464: the need to hold the entire contents in memory,
4465: potentially supporting very large files.
4466: Streaming is automatically set for S/MIME signing with detached
4467: data if the output format is SMIME;
4468: it is currently off by default for all other operations.
4469: .It Fl inform Ar DER | PEM | SMIME
4470: This specifies the input format for the PKCS#7 structure.
4471: The default is
4472: .Em SMIME ,
4473: which reads an
4474: .Em S/MIME
4475: format message.
4476: .Ar PEM
4477: and
4478: .Ar DER
4479: format change this to expect PEM and DER format PKCS#7 structures
4480: instead.
4481: This currently only affects the input format of the PKCS#7
4482: structure; if no PKCS#7 structure is being input (for example with
4483: .Fl encrypt
4484: or
4485: .Fl sign ) ,
4486: this option has no effect.
4487: .It Fl inkey Ar file
4488: The private key to use when signing or decrypting.
4489: This must match the corresponding certificate.
4490: If this option is not specified, the private key must be included
4491: in the certificate file specified with
4492: the
4493: .Fl recip
4494: or
4495: .Fl signer
4496: file.
4497: When signing,
4498: this option can be used multiple times to specify successive keys.
1.22 bcook 4499: .It Fl keyform Ar PEM
1.1 jsing 4500: Input private key format.
4501: .It Fl md Ar digest
4502: The digest algorithm to use when signing or resigning.
4503: If not present then the default digest algorithm for the signing key is used
4504: (usually SHA1).
4505: .It Fl noattr
4506: Normally, when a message is signed a set of attributes are included which
4507: include the signing time and supported symmetric algorithms.
4508: With this option they are not included.
4509: .It Fl nocerts
4510: When signing a message, the signer's certificate is normally included;
4511: with this option it is excluded.
4512: This will reduce the size of the signed message but the verifier must
4513: have a copy of the signer's certificate available locally (passed using the
4514: .Fl certfile
4515: option, for example).
4516: .It Fl nochain
4517: Do not do chain verification of signers' certificates: that is,
4518: don't use the certificates in the signed message as untrusted CAs.
4519: .It Fl nodetach
4520: When signing a message use opaque signing: this form is more resistant
4521: to translation by mail relays but it cannot be read by mail agents that
4522: do not support
4523: .Em S/MIME .
4524: Without this option cleartext signing with the
4525: .Em MIME
4526: type multipart/signed is used.
4527: .It Fl noindef
4528: Disable streaming I/O where it would produce an encoding of indefinite length.
4529: This option currently has no effect.
4530: In future streaming will be enabled by default on all relevant operations
4531: and this option will disable it.
4532: .It Fl nointern
4533: When verifying a message, normally certificates
4534: .Pq if any
4535: included in the message are searched for the signing certificate.
4536: With this option, only the certificates specified in the
4537: .Fl certfile
4538: option are used.
4539: The supplied certificates can still be used as untrusted CAs however.
4540: .It Fl nosigs
4541: Don't try to verify the signatures on the message.
4542: .It Fl noverify
4543: Do not verify the signer's certificate of a signed message.
4544: .It Fl out Ar file
4545: The message text that has been decrypted or verified, or the output
4546: .Em MIME
4547: format message that has been signed or verified.
4548: .It Fl outform Ar DER | PEM | SMIME
4549: This specifies the output format for the PKCS#7 structure.
4550: The default is
4551: .Em SMIME ,
4552: which writes an
4553: .Em S/MIME
4554: format message.
4555: .Ar PEM
4556: and
4557: .Ar DER
4558: format change this to write PEM and DER format PKCS#7 structures
4559: instead.
4560: This currently only affects the output format of the PKCS#7
4561: structure; if no PKCS#7 structure is being output (for example with
4562: .Fl verify
4563: or
4564: .Fl decrypt )
4565: this option has no effect.
4566: .It Fl passin Ar arg
4567: The key password source.
4568: .It Fl recip Ar file
4569: The recipients certificate when decrypting a message.
4570: This certificate
4571: must match one of the recipients of the message or an error occurs.
4572: .It Fl signer Ar file
4573: A signing certificate when signing or resigning a message;
4574: this option can be used multiple times if more than one signer is required.
4575: If a message is being verified, the signer's certificates will be
4576: written to this file if the verification was successful.
4577: .It Fl stream
4578: The same as
4579: .Fl indef .
4580: .It Fl text
4581: This option adds plain text
4582: .Pq text/plain
4583: .Em MIME
4584: headers to the supplied message if encrypting or signing.
4585: If decrypting or verifying, it strips off text headers:
4586: if the decrypted or verified message is not of
4587: .Em MIME
4588: type text/plain then an error occurs.
4589: .El
4590: .Sh SMIME NOTES
4591: The
4592: .Em MIME
4593: message must be sent without any blank lines between the
4594: headers and the output.
4595: Some mail programs will automatically add a blank line.
1.3 jmc 4596: Piping the mail directly to an MTA is one way to
1.1 jsing 4597: achieve the correct format.
4598: .Pp
4599: The supplied message to be signed or encrypted must include the
4600: necessary
4601: .Em MIME
4602: headers or many
4603: .Em S/MIME
4604: clients won't display it properly
4605: .Pq if at all .
4606: You can use the
4607: .Fl text
4608: option to automatically add plain text headers.
4609: .Pp
4610: A
4611: .Qq signed and encrypted
4612: message is one where a signed message is then encrypted.
4613: This can be produced by encrypting an already signed message:
4614: see the
4615: .Sx SMIME EXAMPLES
4616: section.
4617: .Pp
4618: This version of the program only allows one signer per message, but it
4619: will verify multiple signers on received messages.
4620: Some
4621: .Em S/MIME
4622: clients choke if a message contains multiple signers.
4623: It is possible to sign messages
4624: .Qq in parallel
4625: by signing an already signed message.
4626: .Pp
4627: The options
4628: .Fl encrypt
4629: and
4630: .Fl decrypt
4631: reflect common usage in
4632: .Em S/MIME
4633: clients.
4634: Strictly speaking these process PKCS#7 enveloped data: PKCS#7
4635: encrypted data is used for other purposes.
4636: .Pp
4637: The
4638: .Fl resign
4639: option uses an existing message digest when adding a new signer.
4640: This means that attributes must be present in at least one existing
4641: signer using the same message digest or this operation will fail.
4642: .Pp
4643: The
4644: .Fl stream
4645: and
4646: .Fl indef
4647: options enable experimental streaming I/O support.
4648: As a result the encoding is BER using indefinite length constructed encoding
4649: and no longer DER.
4650: Streaming is supported for the
4651: .Fl encrypt
4652: and
4653: .Fl sign
4654: operations if the content is not detached.
4655: .Pp
4656: Streaming is always used for the
4657: .Fl sign
4658: operation with detached data
4659: but since the content is no longer part of the PKCS#7 structure
4660: the encoding remains DER.
4661: .Sh SMIME EXIT CODES
4662: .Bl -tag -width "XXXX"
4663: .It Ar 0
4664: The operation was completely successful.
4665: .It Ar 1
4666: An error occurred parsing the command options.
4667: .It Ar 2
4668: One of the input files could not be read.
4669: .It Ar 3
4670: An error occurred creating the PKCS#7 file or when reading the
4671: .Em MIME
4672: message.
4673: .It Ar 4
4674: An error occurred decrypting or verifying the message.
4675: .It Ar 5
4676: The message was verified correctly, but an error occurred writing out
4677: the signer's certificates.
4678: .El
4679: .Sh SMIME EXAMPLES
4680: Create a cleartext signed message:
4681: .Bd -literal -offset indent
4682: $ openssl smime -sign -in message.txt -text -out mail.msg \e
4683: -signer mycert.pem
4684: .Ed
4685: .Pp
4686: Create an opaque signed message:
4687: .Bd -literal -offset indent
4688: $ openssl smime -sign -in message.txt -text -out mail.msg \e
4689: -nodetach -signer mycert.pem
4690: .Ed
4691: .Pp
4692: Create a signed message, include some additional certificates and
4693: read the private key from another file:
4694: .Bd -literal -offset indent
4695: $ openssl smime -sign -in in.txt -text -out mail.msg \e
4696: -signer mycert.pem -inkey mykey.pem -certfile mycerts.pem
4697: .Ed
4698: .Pp
4699: Create a signed message with two signers:
4700: .Bd -literal -offset indent
4701: openssl smime -sign -in message.txt -text -out mail.msg \e
4702: -signer mycert.pem -signer othercert.pem
4703: .Ed
4704: .Pp
4705: Send a signed message under
4706: .Ux
4707: directly to
4708: .Xr sendmail 8 ,
4709: including headers:
4710: .Bd -literal -offset indent
4711: $ openssl smime -sign -in in.txt -text -signer mycert.pem \e
4712: -from steve@openssl.org -to someone@somewhere \e
4713: -subject "Signed message" | sendmail someone@somewhere
4714: .Ed
4715: .Pp
4716: Verify a message and extract the signer's certificate if successful:
4717: .Bd -literal -offset indent
4718: $ openssl smime -verify -in mail.msg -signer user.pem \e
4719: -out signedtext.txt
4720: .Ed
4721: .Pp
4722: Send encrypted mail using triple DES:
4723: .Bd -literal -offset indent
4724: $ openssl smime -encrypt -in in.txt -from steve@openssl.org \e
4725: -to someone@somewhere -subject "Encrypted message" \e
4726: -des3 -out mail.msg user.pem
4727: .Ed
4728: .Pp
4729: Sign and encrypt mail:
4730: .Bd -literal -offset indent
4731: $ openssl smime -sign -in ml.txt -signer my.pem -text | \e
4732: openssl smime -encrypt -out mail.msg \e
4733: -from steve@openssl.org -to someone@somewhere \e
4734: -subject "Signed and Encrypted message" -des3 user.pem
4735: .Ed
4736: .Pp
4737: .Sy Note :
4738: The encryption command does not include the
4739: .Fl text
4740: option because the message being encrypted already has
4741: .Em MIME
4742: headers.
4743: .Pp
4744: Decrypt mail:
4745: .Bd -literal -offset indent
4746: $ openssl smime -decrypt -in mail.msg -recip mycert.pem \e
4747: -inkey key.pem"
4748: .Ed
4749: .Pp
4750: The output from Netscape form signing is a PKCS#7 structure with the
4751: detached signature format.
4752: You can use this program to verify the signature by line wrapping the
4753: base64-encoded structure and surrounding it with:
4754: .Bd -unfilled -offset indent
4755: -----BEGIN PKCS7-----
4756: -----END PKCS7-----
4757: .Ed
4758: .Pp
4759: and using the command:
4760: .Bd -literal -offset indent
4761: $ openssl smime -verify -inform PEM -in signature.pem \e
4762: -content content.txt
4763: .Ed
4764: .Pp
4765: Alternatively, you can base64 decode the signature and use:
4766: .Bd -literal -offset indent
4767: $ openssl smime -verify -inform DER -in signature.der \e
4768: -content content.txt
4769: .Ed
4770: .Pp
4771: Create an encrypted message using 128-bit AES:
4772: .Bd -literal -offset indent
4773: openssl smime -encrypt -in plain.txt -aes128 \e
4774: -out mail.msg cert.pem
4775: .Ed
4776: .Pp
4777: Add a signer to an existing message:
4778: .Bd -literal -offset indent
4779: openssl smime -resign -in mail.msg -signer newsign.pem \e
4780: -out mail2.msg
4781: .Ed
4782: .Sh SMIME BUGS
4783: The
4784: .Em MIME
4785: parser isn't very clever: it seems to handle most messages that I've thrown
4786: at it, but it may choke on others.
4787: .Pp
4788: The code currently will only write out the signer's certificate to a file:
4789: if the signer has a separate encryption certificate this must be manually
4790: extracted.
4791: There should be some heuristic that determines the correct encryption
4792: certificate.
4793: .Pp
4794: Ideally, a database should be maintained of a certificate for each email
4795: address.
4796: .Pp
4797: The code doesn't currently take note of the permitted symmetric encryption
4798: algorithms as supplied in the
4799: .Em SMIMECapabilities
4800: signed attribute.
4801: This means the user has to manually include the correct encryption algorithm.
4802: It should store the list of permitted ciphers in a database and only use those.
4803: .Pp
4804: No revocation checking is done on the signer's certificate.
4805: .Pp
4806: The current code can only handle
4807: .Em S/MIME
4808: v2 messages; the more complex
4809: .Em S/MIME
4810: v3 structures may cause parsing errors.
4811: .Sh SMIME HISTORY
4812: The use of multiple
4813: .Fl signer
4814: options and the
4815: .Fl resign
4816: command were first added in
4817: .Nm OpenSSL
4818: 1.0.0.
4819: .\"
4820: .\" SPEED
4821: .\"
4822: .Sh SPEED
4823: .nr nS 1
4824: .Nm "openssl speed"
4825: .Bk -words
4826: .Op Cm aes
4827: .Op Cm aes-128-cbc
4828: .Op Cm aes-192-cbc
4829: .Op Cm aes-256-cbc
1.25 bcook 4830: .Op Cm aes-128-gcm
4831: .Op Cm aes-256-gcm
1.1 jsing 4832: .Op Cm blowfish
4833: .Op Cm bf-cbc
4834: .Op Cm cast
4835: .Op Cm cast-cbc
1.25 bcook 4836: .Op Cm chacha20-poly1305
1.1 jsing 4837: .Op Cm des
4838: .Op Cm des-cbc
4839: .Op Cm des-ede3
4840: .Op Cm dsa
4841: .Op Cm dsa512
4842: .Op Cm dsa1024
4843: .Op Cm dsa2048
4844: .Op Cm hmac
1.28 doug 4845: .Op Cm md4
1.1 jsing 4846: .Op Cm md5
4847: .Op Cm rc2
4848: .Op Cm rc2-cbc
4849: .Op Cm rc4
4850: .Op Cm rmd160
4851: .Op Cm rsa
4852: .Op Cm rsa512
4853: .Op Cm rsa1024
4854: .Op Cm rsa2048
4855: .Op Cm rsa4096
4856: .Op Cm sha1
4857: .Op Fl decrypt
4858: .Op Fl elapsed
4859: .Op Fl evp Ar e
4860: .Op Fl mr
4861: .Op Fl multi Ar number
4862: .Ek
4863: .nr nS 0
4864: .Pp
4865: The
4866: .Nm speed
4867: command is used to test the performance of cryptographic algorithms.
4868: .Bl -tag -width "XXXX"
4869: .It Bq Cm zero or more test algorithms
4870: If any options are given,
4871: .Nm speed
4872: tests those algorithms, otherwise all of the above are tested.
4873: .It Fl decrypt
4874: Time decryption instead of encryption
4875: .Pq only EVP .
4876: .It Fl elapsed
4877: Measure time in real time instead of CPU user time.
4878: .It Fl evp Ar e
4879: Use EVP
4880: .Ar e .
4881: .It Fl mr
4882: Produce machine readable output.
4883: .It Fl multi Ar number
4884: Run
4885: .Ar number
4886: benchmarks in parallel.
4887: .El
4888: .\"
4889: .\" TS
4890: .\"
4891: .Sh TS
4892: .nr nS 1
4893: .Nm "openssl ts"
4894: .Bk -words
4895: .Fl query
1.29 bcook 4896: .Op Fl md4 | md5 | ripemd160 | sha1
1.1 jsing 4897: .Op Fl cert
4898: .Op Fl config Ar configfile
4899: .Op Fl data Ar file_to_hash
4900: .Op Fl digest Ar digest_bytes
4901: .Op Fl in Ar request.tsq
4902: .Op Fl no_nonce
4903: .Op Fl out Ar request.tsq
4904: .Op Fl policy Ar object_id
4905: .Op Fl text
4906: .Ek
4907: .nr nS 0
4908: .Pp
4909: .nr nS 1
4910: .Nm "openssl ts"
4911: .Bk -words
4912: .Fl reply
4913: .Op Fl chain Ar certs_file.pem
4914: .Op Fl config Ar configfile
4915: .Op Fl in Ar response.tsr
4916: .Op Fl inkey Ar private.pem
4917: .Op Fl out Ar response.tsr
4918: .Op Fl passin Ar arg
4919: .Op Fl policy Ar object_id
4920: .Op Fl queryfile Ar request.tsq
4921: .Op Fl section Ar tsa_section
4922: .Op Fl signer Ar tsa_cert.pem
4923: .Op Fl text
4924: .Op Fl token_in
4925: .Op Fl token_out
4926: .Ek
4927: .nr nS 0
4928: .Pp
4929: .nr nS 1
4930: .Nm "openssl ts"
4931: .Bk -words
4932: .Fl verify
4933: .Op Fl CAfile Ar trusted_certs.pem
4934: .Op Fl CApath Ar trusted_cert_path
4935: .Op Fl data Ar file_to_hash
4936: .Op Fl digest Ar digest_bytes
4937: .Op Fl in Ar response.tsr
4938: .Op Fl queryfile Ar request.tsq
4939: .Op Fl token_in
4940: .Op Fl untrusted Ar cert_file.pem
4941: .Ek
4942: .nr nS 0
4943: .Pp
4944: The
4945: .Nm ts
4946: command is a basic Time Stamping Authority (TSA) client and server
4947: application as specified in RFC 3161 (Time-Stamp Protocol, TSP).
4948: A TSA can be part of a PKI deployment and its role is to provide long
4949: term proof of the existence of a certain datum before a particular time.
4950: Here is a brief description of the protocol:
4951: .Bl -enum
4952: .It
4953: The TSA client computes a one-way hash value for a data file and sends
4954: the hash to the TSA.
4955: .It
4956: The TSA attaches the current date and time to the received hash value,
4957: signs them and sends the time stamp token back to the client.
4958: By creating this token the TSA certifies the existence of the original
4959: data file at the time of response generation.
4960: .It
4961: The TSA client receives the time stamp token and verifies the
4962: signature on it.
4963: It also checks if the token contains the same hash
4964: value that it had sent to the TSA.
4965: .El
4966: .Pp
4967: There is one DER-encoded protocol data unit defined for transporting a time
4968: stamp request to the TSA and one for sending the time stamp response
4969: back to the client.
4970: The
4971: .Nm ts
4972: command has three main functions:
4973: creating a time stamp request based on a data file;
4974: creating a time stamp response based on a request;
4975: and verifying if a response corresponds
4976: to a particular request or a data file.
4977: .Pp
4978: There is no support for sending the requests/responses automatically
4979: over HTTP or TCP yet as suggested in RFC 3161.
4980: Users must send the requests either by FTP or email.
4981: .Pp
4982: The
4983: .Fl query
4984: switch can be used for creating and printing a time stamp
4985: request with the following options:
4986: .Bl -tag -width Ds
4987: .It Fl cert
4988: The TSA is expected to include its signing certificate in the
4989: response.
4990: .It Fl config Ar configfile
4991: The configuration file to use.
4992: This option overrides the
4993: .Ev OPENSSL_CONF
4994: environment variable.
4995: Only the OID section of the config file is used with the
4996: .Fl query
4997: command.
4998: .It Fl data Ar file_to_hash
4999: The data file for which the time stamp request needs to be created.
5000: stdin is the default if neither the
5001: .Fl data
5002: nor the
5003: .Fl digest
5004: option is specified.
5005: .It Fl digest Ar digest_bytes
5006: It is possible to specify the message imprint explicitly without the data
5007: file.
5008: The imprint must be specified in a hexadecimal format,
5009: two characters per byte,
5010: the bytes optionally separated by colons (e.g. 1A:F6:01:... or 1AF601...).
5011: The number of bytes must match the message digest algorithm in use.
5012: .It Fl in Ar request.tsq
5013: This option specifies a previously created time stamp request in DER
5014: format that will be printed into the output file.
5015: Useful when you need to examine the content of a request in human-readable
5016: format.
1.28 doug 5017: .It Fl md4|md5|ripemd160|sha|sha1
1.1 jsing 5018: The message digest to apply to the data file.
5019: It supports all the message digest algorithms that are supported by the
5020: .Nm dgst
5021: command.
5022: The default is SHA-1.
5023: .It Fl no_nonce
5024: No nonce is specified in the request if this option is given.
5025: Otherwise a 64-bit long pseudo-random none is
5026: included in the request.
5027: It is recommended to use nonce to protect against replay-attacks.
5028: .It Fl out Ar request.tsq
5029: Name of the output file to which the request will be written.
5030: The default is stdout.
5031: .It Fl policy Ar object_id
5032: The policy that the client expects the TSA to use for creating the
5033: time stamp token.
5034: Either the dotted OID notation or OID names defined
5035: in the config file can be used.
5036: If no policy is requested the TSA will
5037: use its own default policy.
5038: .It Fl text
5039: If this option is specified the output is in human-readable text format
5040: instead of DER.
5041: .El
5042: .Pp
5043: A time stamp response (TimeStampResp) consists of a response status
5044: and the time stamp token itself (ContentInfo),
5045: if the token generation was successful.
5046: The
5047: .Fl reply
5048: command is for creating a time stamp
5049: response or time stamp token based on a request and printing the
5050: response/token in human-readable format.
5051: If
5052: .Fl token_out
5053: is not specified the output is always a time stamp response (TimeStampResp),
5054: otherwise it is a time stamp token (ContentInfo).
5055: .Bl -tag -width Ds
5056: .It Fl chain Ar certs_file.pem
5057: The collection of certificates, in PEM format,
5058: that will be included in the response
5059: in addition to the signer certificate if the
5060: .Fl cert
5061: option was used for the request.
5062: This file is supposed to contain the certificate chain
5063: for the signer certificate from its issuer upwards.
5064: The
5065: .Fl reply
5066: command does not build a certificate chain automatically.
5067: .It Fl config Ar configfile
5068: The configuration file to use.
5069: This option overrides the
5070: .Ev OPENSSL_CONF
5071: environment variable.
5072: See
5073: .Sx TS CONFIGURATION FILE OPTIONS
5074: for configurable variables.
5075: .It Fl in Ar response.tsr
5076: Specifies a previously created time stamp response or time stamp token, if
5077: .Fl token_in
5078: is also specified,
5079: in DER format that will be written to the output file.
5080: This option does not require a request;
5081: it is useful, for example,
5082: when you need to examine the content of a response or token
5083: or you want to extract the time stamp token from a response.
5084: If the input is a token and the output is a time stamp response a default
5085: .Dq granted
5086: status info is added to the token.
5087: .It Fl inkey Ar private.pem
5088: The signer private key of the TSA in PEM format.
5089: Overrides the
5090: .Cm signer_key
5091: config file option.
5092: .It Fl out Ar response.tsr
5093: The response is written to this file.
5094: The format and content of the file depends on other options (see
5095: .Fl text
5096: and
5097: .Fl token_out ) .
5098: The default is stdout.
5099: .It Fl passin Ar arg
5100: The key password source.
5101: .It Fl policy Ar object_id
5102: The default policy to use for the response unless the client
5103: explicitly requires a particular TSA policy.
5104: The OID can be specified either in dotted notation or with its name.
5105: Overrides the
5106: .Cm default_policy
5107: config file option.
5108: .It Fl queryfile Ar request.tsq
5109: The name of the file containing a DER-encoded time stamp request.
5110: .It Fl section Ar tsa_section
5111: The name of the config file section containing the settings for the
5112: response generation.
5113: If not specified the default TSA section is used; see
5114: .Sx TS CONFIGURATION FILE OPTIONS
5115: for details.
5116: .It Fl signer Ar tsa_cert.pem
5117: The signer certificate of the TSA in PEM format.
5118: The TSA signing certificate must have exactly one extended key usage
5119: assigned to it: timeStamping.
5120: The extended key usage must also be critical,
5121: otherwise the certificate is going to be refused.
5122: Overrides the
5123: .Cm signer_cert
5124: variable of the config file.
5125: .It Fl text
5126: If this option is specified the output is human-readable text format
5127: instead of DER.
5128: .It Fl token_in
5129: This flag can be used together with the
5130: .Fl in
5131: option and indicates that the input is a DER-encoded time stamp token
5132: (ContentInfo) instead of a time stamp response (TimeStampResp).
5133: .It Fl token_out
5134: The output is a time stamp token (ContentInfo) instead of time stamp
5135: response (TimeStampResp).
5136: .El
5137: .Pp
5138: The
5139: .Fl verify
5140: command is for verifying if a time stamp response or time stamp token
5141: is valid and matches a particular time stamp request or data file.
5142: The
5143: .Fl verify
5144: command does not use the configuration file.
5145: .Bl -tag -width Ds
5146: .It Fl CAfile Ar trusted_certs.pem
5147: The name of the file containing a set of trusted self-signed CA
5148: certificates in PEM format.
5149: See the similar option of
5150: .Nm verify
5151: for additional details.
5152: Either this option or
5153: .Fl CApath
5154: must be specified.
5155: .It Fl CApath Ar trusted_cert_path
5156: The name of the directory containing the trused CA certificates of the
5157: client.
5158: See the similar option of
5159: .Nm verify
5160: for additional details.
5161: Either this option or
5162: .Fl CAfile
5163: must be specified.
5164: .It Fl data Ar file_to_hash
5165: The response or token must be verified against
5166: .Ar file_to_hash .
5167: The file is hashed with the message digest algorithm specified in the token.
5168: The
5169: .Fl digest
5170: and
5171: .Fl queryfile
5172: options must not be specified with this one.
5173: .It Fl digest Ar digest_bytes
5174: The response or token must be verified against the message digest specified
5175: with this option.
5176: The number of bytes must match the message digest algorithm
5177: specified in the token.
5178: The
5179: .Fl data
5180: and
5181: .Fl queryfile
5182: options must not be specified with this one.
5183: .It Fl in Ar response.tsr
5184: The time stamp response that needs to be verified, in DER format.
5185: This option in mandatory.
5186: .It Fl queryfile Ar request.tsq
5187: The original time stamp request, in DER format.
5188: The
5189: .Fl data
5190: and
5191: .Fl digest
5192: options must not be specified with this one.
5193: .It Fl token_in
5194: This flag can be used together with the
5195: .Fl in
5196: option and indicates that the input is a DER-encoded time stamp token
5197: (ContentInfo) instead of a time stamp response (TimeStampResp).
5198: .It Fl untrusted Ar cert_file.pem
5199: Set of additional untrusted certificates in PEM format which may be
5200: needed when building the certificate chain for the TSA's signing
5201: certificate.
5202: This file must contain the TSA signing certificate and
5203: all intermediate CA certificates unless the response includes them.
5204: .El
5205: .Sh TS CONFIGURATION FILE OPTIONS
5206: The
5207: .Fl query
5208: and
5209: .Fl reply
5210: options make use of a configuration file defined by the
5211: .Ev OPENSSL_CONF
5212: environment variable.
5213: The
5214: .Fl query
5215: option uses only the symbolic OID names section
5216: and it can work without it.
5217: However, the
5218: .Fl reply
5219: option needs the config file for its operation.
5220: .Pp
5221: When there is a command line switch equivalent of a variable the
5222: switch always overrides the settings in the config file.
5223: .Bl -tag -width Ds
5224: .It Cm tsa Ar section , Cm default_tsa
5225: This is the main section and it specifies the name of another section
5226: that contains all the options for the
5227: .Fl reply
5228: option.
5229: This default section can be overridden with the
5230: .Fl section
5231: command line switch.
5232: .It Cm oid_file
5233: See
5234: .Nm ca
5235: for a description.
5236: .It Cm oid_section
5237: See
5238: .Nm ca
5239: for a description.
5240: .It Cm serial
5241: The name of the file containing the hexadecimal serial number of the
5242: last time stamp response created.
5243: This number is incremented by 1 for each response.
5244: If the file does not exist at the time of response
5245: generation a new file is created with serial number 1.
5246: This parameter is mandatory.
5247: .It Cm signer_cert
5248: TSA signing certificate, in PEM format.
5249: The same as the
5250: .Fl signer
5251: command line option.
5252: .It Cm certs
5253: A file containing a set of PEM-encoded certificates that need to be
5254: included in the response.
5255: The same as the
5256: .Fl chain
5257: command line option.
5258: .It Cm signer_key
5259: The private key of the TSA, in PEM format.
5260: The same as the
5261: .Fl inkey
5262: command line option.
5263: .It Cm default_policy
5264: The default policy to use when the request does not mandate any policy.
5265: The same as the
5266: .Fl policy
5267: command line option.
5268: .It Cm other_policies
5269: Comma separated list of policies that are also acceptable by the TSA
5270: and used only if the request explicitly specifies one of them.
5271: .It Cm digests
5272: The list of message digest algorithms that the TSA accepts.
5273: At least one algorithm must be specified.
5274: This parameter is mandatory.
5275: .It Cm accuracy
5276: The accuracy of the time source of the TSA in seconds, milliseconds
5277: and microseconds.
5278: For example, secs:1, millisecs:500, microsecs:100.
5279: If any of the components is missing,
5280: zero is assumed for that field.
5281: .It Cm clock_precision_digits
5282: Specifies the maximum number of digits, which represent the fraction of
5283: seconds, that need to be included in the time field.
5284: The trailing zeroes must be removed from the time,
5285: so there might actually be fewer digits,
5286: or no fraction of seconds at all.
5287: The maximum value is 6;
5288: the default is 0.
5289: .It Cm ordering
5290: If this option is yes,
5291: the responses generated by this TSA can always be ordered,
5292: even if the time difference between two responses is less
5293: than the sum of their accuracies.
5294: The default is no.
5295: .It Cm tsa_name
5296: Set this option to yes if the subject name of the TSA must be included in
5297: the TSA name field of the response.
5298: The default is no.
5299: .It Cm ess_cert_id_chain
5300: The SignedData objects created by the TSA always contain the
5301: certificate identifier of the signing certificate in a signed
5302: attribute (see RFC 2634, Enhanced Security Services).
5303: If this option is set to yes and either the
5304: .Cm certs
5305: variable or the
5306: .Fl chain
5307: option is specified then the certificate identifiers of the chain will also
5308: be included in the SigningCertificate signed attribute.
5309: If this variable is set to no,
5310: only the signing certificate identifier is included.
5311: The default is no.
5312: .El
5313: .Sh TS ENVIRONMENT VARIABLES
5314: .Ev OPENSSL_CONF
5315: contains the path of the configuration file and can be
5316: overridden by the
5317: .Fl config
5318: command line option.
5319: .Sh TS EXAMPLES
5320: All the examples below presume that
5321: .Ev OPENSSL_CONF
5322: is set to a proper configuration file,
5323: e.g. the example configuration file
5324: .Pa openssl/apps/openssl.cnf
5325: will do.
5326: .Pp
5327: To create a time stamp request for design1.txt with SHA-1
5328: without nonce and policy and no certificate is required in the response:
5329: .Bd -literal -offset indent
5330: $ openssl ts -query -data design1.txt -no_nonce \e
5331: -out design1.tsq
5332: .Ed
5333: .Pp
5334: To create a similar time stamp request but specifying the message imprint
5335: explicitly:
5336: .Bd -literal -offset indent
5337: $ openssl ts -query \e
5338: -digest b7e5d3f93198b38379852f2c04e78d73abdd0f4b \e
5339: -no_nonce -out design1.tsq
5340: .Ed
5341: .Pp
5342: To print the content of the previous request in human readable format:
5343: .Bd -literal -offset indent
5344: $ openssl ts -query -in design1.tsq -text
5345: .Ed
5346: .Pp
5347: To create a time stamp request which includes the MD5 digest
5348: of design2.txt, requests the signer certificate and nonce,
5349: specifies a policy ID
5350: (assuming the tsa_policy1 name is defined in the
5351: OID section of the config file):
5352: .Bd -literal -offset indent
5353: $ openssl ts -query -data design2.txt -md5 \e
5354: -policy tsa_policy1 -cert -out design2.tsq
5355: .Ed
5356: .Pp
5357: Before generating a response,
5358: a signing certificate must be created for the TSA that contains the
5359: .Cm timeStamping
5360: critical extended key usage extension
5361: without any other key usage extensions.
5362: You can add the
5363: .Dq extendedKeyUsage = critical,timeStamping
5364: line to the user certificate section
5365: of the config file to generate a proper certificate.
5366: See the
5367: .Nm req ,
5368: .Nm ca ,
5369: and
5370: .Nm x509
5371: commands for instructions.
5372: The examples below assume that cacert.pem contains the certificate of the CA,
5373: tsacert.pem is the signing certificate issued by cacert.pem and
5374: tsakey.pem is the private key of the TSA.
5375: .Pp
5376: To create a time stamp response for a request:
5377: .Bd -literal -offset indent
5378: $ openssl ts -reply -queryfile design1.tsq -inkey tsakey.pem \e
5379: -signer tsacert.pem -out design1.tsr
5380: .Ed
5381: .Pp
5382: If you want to use the settings in the config file you could just write:
5383: .Bd -literal -offset indent
5384: $ openssl ts -reply -queryfile design1.tsq -out design1.tsr
5385: .Ed
5386: .Pp
5387: To print a time stamp reply to stdout in human readable format:
5388: .Bd -literal -offset indent
5389: $ openssl ts -reply -in design1.tsr -text
5390: .Ed
5391: .Pp
5392: To create a time stamp token instead of time stamp response:
5393: .Bd -literal -offset indent
5394: $ openssl ts -reply -queryfile design1.tsq \e
5395: -out design1_token.der -token_out
5396: .Ed
5397: .Pp
5398: To print a time stamp token to stdout in human readable format:
5399: .Bd -literal -offset indent
5400: $ openssl ts -reply -in design1_token.der -token_in \e
5401: -text -token_out
5402: .Ed
5403: .Pp
5404: To extract the time stamp token from a response:
5405: .Bd -literal -offset indent
5406: $ openssl ts -reply -in design1.tsr -out design1_token.der \e
5407: -token_out
5408: .Ed
5409: .Pp
5410: To add
5411: .Dq granted
5412: status info to a time stamp token thereby creating a valid response:
5413: .Bd -literal -offset indent
5414: $ openssl ts -reply -in design1_token.der \e
5415: -token_in -out design1.tsr
5416: .Ed
5417: .Pp
5418: To verify a time stamp reply against a request:
5419: .Bd -literal -offset indent
5420: $ openssl ts -verify -queryfile design1.tsq -in design1.tsr \e
5421: -CAfile cacert.pem -untrusted tsacert.pem
5422: .Ed
5423: .Pp
5424: To verify a time stamp reply that includes the certificate chain:
5425: .Bd -literal -offset indent
5426: $ openssl ts -verify -queryfile design2.tsq -in design2.tsr \e
5427: -CAfile cacert.pem
5428: .Ed
5429: .Pp
5430: To verify a time stamp token against the original data file:
5431: .Bd -literal -offset indent
5432: $ openssl ts -verify -data design2.txt -in design2.tsr \e
5433: -CAfile cacert.pem
5434: .Ed
5435: .Pp
5436: To verify a time stamp token against a message imprint:
5437: .Bd -literal -offset indent
5438: $ openssl ts -verify \e
5439: -digest b7e5d3f93198b38379852f2c04e78d73abdd0f4b \e
5440: -in design2.tsr -CAfile cacert.pem
5441: .Ed
5442: .Sh TS BUGS
5443: No support for time stamps over SMTP, though it is quite easy
5444: to implement an automatic email-based TSA with
5445: .Xr procmail
5446: and
5447: .Xr perl 1 .
5448: Pure TCP/IP is not supported.
5449: .Pp
5450: The file containing the last serial number of the TSA is not
5451: locked when being read or written.
5452: This is a problem if more than one instance of
5453: .Nm OpenSSL
5454: is trying to create a time stamp
5455: response at the same time.
5456: .Pp
5457: Look for the FIXME word in the source files.
5458: .Pp
5459: The source code should really be reviewed by somebody else, too.
5460: .Pp
5461: More testing is needed.
5462: .Sh TS AUTHORS
5463: .An Zoltan Glozik Aq Mt zglozik@opentsa.org ,
5464: OpenTSA project
5465: .Pq Lk http://www.opentsa.org .
5466: .\"
5467: .\" SPKAC
5468: .\"
5469: .Sh SPKAC
5470: .nr nS 1
5471: .Nm "openssl spkac"
5472: .Bk -words
5473: .Op Fl challenge Ar string
5474: .Op Fl in Ar file
5475: .Op Fl key Ar keyfile
5476: .Op Fl noout
5477: .Op Fl out Ar file
5478: .Op Fl passin Ar arg
5479: .Op Fl pubkey
5480: .Op Fl spkac Ar spkacname
5481: .Op Fl spksect Ar section
5482: .Op Fl verify
5483: .Ek
5484: .nr nS 0
5485: .Pp
5486: The
5487: .Nm spkac
5488: command processes Netscape signed public key and challenge
5489: .Pq SPKAC
5490: files.
5491: It can print out their contents, verify the signature,
5492: and produce its own SPKACs from a supplied private key.
5493: .Pp
5494: The options are as follows:
5495: .Bl -tag -width Ds
5496: .It Fl challenge Ar string
5497: Specifies the challenge string if an SPKAC is being created.
5498: .It Fl in Ar file
5499: This specifies the input
5500: .Ar file
5501: to read from, or standard input if this option is not specified.
5502: Ignored if the
5503: .Fl key
5504: option is used.
5505: .It Fl key Ar keyfile
5506: Create an SPKAC file using the private key in
5507: .Ar keyfile .
5508: The
5509: .Fl in , noout , spksect ,
5510: and
5511: .Fl verify
5512: options are ignored if present.
5513: .It Fl noout
5514: Don't output the text version of the SPKAC
5515: .Pq not used if an SPKAC is being created .
5516: .It Fl out Ar file
5517: Specifies the output
5518: .Ar file
5519: to write to, or standard output by default.
5520: .It Fl passin Ar arg
5521: The key password source.
5522: .It Fl pubkey
5523: Output the public key of an SPKAC
5524: .Pq not used if an SPKAC is being created .
5525: .It Fl spkac Ar spkacname
5526: Allows an alternative name for the variable containing the SPKAC.
5527: The default is "SPKAC".
5528: This option affects both generated and input SPKAC files.
5529: .It Fl spksect Ar section
5530: Allows an alternative name for the
5531: .Ar section
5532: containing the SPKAC.
5533: The default is the default section.
5534: .It Fl verify
5535: Verifies the digital signature on the supplied SPKAC.
5536: .El
5537: .Sh SPKAC EXAMPLES
5538: Print out the contents of an SPKAC:
5539: .Pp
5540: .Dl $ openssl spkac -in spkac.cnf
5541: .Pp
5542: Verify the signature of an SPKAC:
5543: .Pp
5544: .Dl $ openssl spkac -in spkac.cnf -noout -verify
5545: .Pp
5546: Create an SPKAC using the challenge string
5547: .Qq hello :
5548: .Pp
5549: .Dl $ openssl spkac -key key.pem -challenge hello -out spkac.cnf
5550: .Pp
5551: Example of an SPKAC,
5552: .Pq long lines split up for clarity :
5553: .Bd -unfilled -offset indent
5554: SPKAC=MIG5MGUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEA1cCoq2Wa3Ixs47uI7F\e
5555: PVwHVIPDx5yso105Y6zpozam135a8R0CpoRvkkigIyXfcCjiVi5oWk+6FfPaD03u\e
5556: PFoQIDAQABFgVoZWxsbzANBgkqhkiG9w0BAQQFAANBAFpQtY/FojdwkJh1bEIYuc\e
5557: 2EeM2KHTWPEepWYeawvHD0gQ3DngSC75YCWnnDdq+NQ3F+X4deMx9AaEglZtULwV\e
5558: 4=
5559: .Ed
5560: .Sh SPKAC NOTES
5561: A created SPKAC with suitable DN components appended can be fed into
5562: the
5563: .Nm ca
5564: utility.
5565: .Pp
5566: SPKACs are typically generated by Netscape when a form is submitted
5567: containing the
5568: .Em KEYGEN
5569: tag as part of the certificate enrollment process.
5570: .Pp
5571: The challenge string permits a primitive form of proof of possession
5572: of private key.
5573: By checking the SPKAC signature and a random challenge
5574: string, some guarantee is given that the user knows the private key
5575: corresponding to the public key being certified.
5576: This is important in some applications.
5577: Without this it is possible for a previous SPKAC
5578: to be used in a
5579: .Qq replay attack .
5580: .\"
5581: .\" VERIFY
5582: .\"
5583: .Sh VERIFY
5584: .nr nS 1
5585: .Nm "openssl verify"
5586: .Bk -words
5587: .Op Fl CAfile Ar file
5588: .Op Fl CApath Ar directory
5589: .Op Fl check_ss_sig
5590: .Op Fl crl_check
5591: .Op Fl crl_check_all
5592: .Op Fl explicit_policy
5593: .Op Fl extended_crl
5594: .Op Fl help
5595: .Op Fl ignore_critical
5596: .Op Fl inhibit_any
5597: .Op Fl inhibit_map
5598: .Op Fl issuer_checks
5599: .Op Fl policy_check
5600: .Op Fl purpose Ar purpose
5601: .Op Fl untrusted Ar file
5602: .Op Fl verbose
5603: .Op Fl x509_strict
5604: .Op Fl
5605: .Op Ar certificates
5606: .Ek
5607: .nr nS 0
5608: .Pp
5609: The
5610: .Nm verify
5611: command verifies certificate chains.
5612: .Pp
5613: The options are as follows:
5614: .Bl -tag -width Ds
5615: .It Fl check_ss_sig
5616: Verify the signature on the self-signed root CA.
5617: This is disabled by default
5618: because it doesn't add any security.
5619: .It Fl CAfile Ar file
5620: A
5621: .Ar file
5622: of trusted certificates.
5623: The
5624: .Ar file
5625: should contain multiple certificates in PEM format, concatenated together.
5626: .It Fl CApath Ar directory
5627: A
5628: .Ar directory
5629: of trusted certificates.
5630: The certificates should have names of the form
5631: .Em hash.0 ,
5632: or have symbolic links to them of this form
5633: ("hash" is the hashed certificate subject name: see the
5634: .Fl hash
5635: option of the
5636: .Nm x509
5637: utility).
5638: The
5639: .Nm c_rehash
5640: script distributed with OpenSSL
5641: will automatically create symbolic links to a directory of certificates.
5642: .It Fl crl_check
5643: Checks end entity certificate validity by attempting to look up a valid CRL.
5644: If a valid CRL cannot be found an error occurs.
5645: .It Fl crl_check_all
5646: Checks the validity of all certificates in the chain by attempting
5647: to look up valid CRLs.
5648: .It Fl explicit_policy
5649: Set policy variable require-explicit-policy (see RFC 3280 et al).
5650: .It Fl extended_crl
5651: Enable extended CRL features such as indirect CRLs and alternate CRL
5652: signing keys.
5653: .It Fl help
5654: Prints out a usage message.
5655: .It Fl ignore_critical
5656: Normally if an unhandled critical extension is present which is not
5657: supported by
5658: .Nm OpenSSL ,
5659: the certificate is rejected (as required by RFC 3280 et al).
5660: If this option is set, critical extensions are ignored.
5661: .It Fl inhibit_any
5662: Set policy variable inhibit-any-policy (see RFC 3280 et al).
5663: .It Fl inhibit_map
5664: Set policy variable inhibit-policy-mapping (see RFC 3280 et al).
5665: .It Fl issuer_checks
5666: Print out diagnostics relating to searches for the issuer certificate
5667: of the current certificate.
5668: This shows why each candidate issuer certificate was rejected.
5669: However the presence of rejection messages
5670: does not itself imply that anything is wrong: during the normal
5671: verify process several rejections may take place.
5672: .It Fl policy_check
5673: Enables certificate policy processing.
5674: .It Fl purpose Ar purpose
5675: The intended use for the certificate.
5676: Without this option no chain verification will be done.
5677: Currently accepted uses are
5678: .Ar sslclient , sslserver ,
5679: .Ar nssslserver , smimesign ,
5680: .Ar smimeencrypt , crlsign ,
5681: .Ar any ,
5682: and
5683: .Ar ocsphelper .
5684: See the
5685: .Sx VERIFY OPERATION
5686: section for more information.
5687: .It Fl untrusted Ar file
5688: A
5689: .Ar file
5690: of untrusted certificates.
5691: The
5692: .Ar file
5693: should contain multiple certificates.
5694: .It Fl verbose
5695: Print extra information about the operations being performed.
5696: .It Fl x509_strict
5697: Disable workarounds for broken certificates which have to be disabled
5698: for strict X.509 compliance.
5699: .It Fl
5700: Marks the last option.
5701: All arguments following this are assumed to be certificate files.
5702: This is useful if the first certificate filename begins with a
5703: .Sq - .
5704: .It Ar certificates
5705: One or more
5706: .Ar certificates
5707: to verify.
5708: If no certificate files are included, an attempt is made to read
5709: a certificate from standard input.
5710: They should all be in PEM format.
5711: .El
5712: .Sh VERIFY OPERATION
5713: The
5714: .Nm verify
5715: program uses the same functions as the internal SSL and S/MIME verification,
5716: therefore this description applies to these verify operations too.
5717: .Pp
5718: There is one crucial difference between the verify operations performed
5719: by the
5720: .Nm verify
5721: program: wherever possible an attempt is made to continue
5722: after an error, whereas normally the verify operation would halt on the
5723: first error.
5724: This allows all the problems with a certificate chain to be determined.
5725: .Pp
5726: The verify operation consists of a number of separate steps:
5727: .Pp
5728: Firstly a certificate chain is built up starting from the supplied certificate
5729: and ending in the root CA.
5730: It is an error if the whole chain cannot be built up.
5731: The chain is built up by looking up the issuer's certificate of the current
5732: certificate.
5733: If a certificate is found which is its own issuer, it is assumed
5734: to be the root CA.
5735: .Pp
5736: The process of
5737: .Qq looking up the issuer's certificate
5738: itself involves a number of steps.
5739: In versions of
5740: .Nm OpenSSL
5741: before 0.9.5a the first certificate whose subject name matched the issuer
5742: of the current certificate was assumed to be the issuer's certificate.
5743: In
5744: .Nm OpenSSL
5745: 0.9.6 and later all certificates whose subject name matches the issuer name
5746: of the current certificate are subject to further tests.
5747: The relevant authority key identifier components of the current certificate
5748: .Pq if present
5749: must match the subject key identifier
5750: .Pq if present
5751: and issuer and serial number of the candidate issuer; in addition the
5752: .Em keyUsage
5753: extension of the candidate issuer
5754: .Pq if present
5755: must permit certificate signing.
5756: .Pp
5757: The lookup first looks in the list of untrusted certificates and if no match
5758: is found the remaining lookups are from the trusted certificates.
5759: The root CA is always looked up in the trusted certificate list: if the
5760: certificate to verify is a root certificate, then an exact match must be
5761: found in the trusted list.
5762: .Pp
5763: The second operation is to check every untrusted certificate's extensions for
5764: consistency with the supplied purpose.
5765: If the
5766: .Fl purpose
5767: option is not included, then no checks are done.
5768: The supplied or
5769: .Qq leaf
5770: certificate must have extensions compatible with the supplied purpose
5771: and all other certificates must also be valid CA certificates.
5772: The precise extensions required are described in more detail in
5773: the
5774: .Sx X.509 CERTIFICATE EXTENSIONS
5775: section below.
5776: .Pp
5777: The third operation is to check the trust settings on the root CA.
5778: The root CA should be trusted for the supplied purpose.
5779: For compatibility with previous versions of
5780: .Nm SSLeay
5781: and
5782: .Nm OpenSSL ,
5783: a certificate with no trust settings is considered to be valid for
5784: all purposes.
5785: .Pp
5786: The final operation is to check the validity of the certificate chain.
5787: The validity period is checked against the current system time and the
5788: .Em notBefore
5789: and
5790: .Em notAfter
5791: dates in the certificate.
5792: The certificate signatures are also checked at this point.
5793: .Pp
5794: If all operations complete successfully, the certificate is considered
5795: valid.
5796: If any operation fails then the certificate is not valid.
5797: .Sh VERIFY DIAGNOSTICS
5798: When a verify operation fails, the output messages can be somewhat cryptic.
5799: The general form of the error message is:
5800: .Bd -unfilled
5801: \& server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024-bit)
5802: \& error 24 at 1 depth lookup:invalid CA certificate
5803: .Ed
5804: .Pp
5805: The first line contains the name of the certificate being verified, followed by
5806: the subject name of the certificate.
5807: The second line contains the error number and the depth.
5808: The depth is the number of the certificate being verified when a
5809: problem was detected starting with zero for the certificate being verified
5810: itself, then 1 for the CA that signed the certificate and so on.
5811: Finally a text version of the error number is presented.
5812: .Pp
5813: An exhaustive list of the error codes and messages is shown below; this also
5814: includes the name of the error code as defined in the header file
1.12 bentley 5815: .In openssl/x509_vfy.h .
1.1 jsing 5816: Some of the error codes are defined but never returned: these are described
5817: as
5818: .Qq unused .
5819: .Bl -tag -width "XXXX"
5820: .It Ar "0 X509_V_OK: ok"
5821: The operation was successful.
5822: .It Ar 2 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT: unable to get issuer certificate
5823: The issuer certificate could not be found: this occurs if the issuer certificate
5824: of an untrusted certificate cannot be found.
5825: .It Ar 3 X509_V_ERR_UNABLE_TO_GET_CRL: unable to get certificate CRL
5826: The CRL of a certificate could not be found.
5827: .It Ar 4 X509_V_ERR_UNABLE_TO_DECRYPT_CERT_SIGNATURE: unable to decrypt certificate's signature
5828: The certificate signature could not be decrypted.
5829: This means that the actual signature value could not be determined rather
5830: than it not matching the expected value.
5831: This is only meaningful for RSA keys.
5832: .It Ar 5 X509_V_ERR_UNABLE_TO_DECRYPT_CRL_SIGNATURE: unable to decrypt CRL's signature
5833: The CRL signature could not be decrypted: this means that the actual
5834: signature value could not be determined rather than it not matching the
5835: expected value.
5836: Unused.
5837: .It Ar 6 X509_V_ERR_UNABLE_TO_DECODE_ISSUER_PUBLIC_KEY: unable to decode issuer public key
5838: The public key in the certificate
5839: .Em SubjectPublicKeyInfo
5840: could not be read.
5841: .It Ar 7 X509_V_ERR_CERT_SIGNATURE_FAILURE: certificate signature failure
5842: The signature of the certificate is invalid.
5843: .It Ar 8 X509_V_ERR_CRL_SIGNATURE_FAILURE: CRL signature failure
5844: The signature of the certificate is invalid.
5845: .It Ar 9 X509_V_ERR_CERT_NOT_YET_VALID: certificate is not yet valid
5846: The certificate is not yet valid: the
5847: .Em notBefore
5848: date is after the current time.
5849: .It Ar 10 X509_V_ERR_CERT_HAS_EXPIRED: certificate has expired
5850: The certificate has expired; that is, the
5851: .Em notAfter
5852: date is before the current time.
5853: .It Ar 11 X509_V_ERR_CRL_NOT_YET_VALID: CRL is not yet valid
5854: The CRL is not yet valid.
5855: .It Ar 12 X509_V_ERR_CRL_HAS_EXPIRED: CRL has expired
5856: The CRL has expired.
5857: .It Ar 13 X509_V_ERR_ERROR_IN_CERT_NOT_BEFORE_FIELD: format error in certificate's notBefore field
5858: The certificate
5859: .Em notBefore
5860: field contains an invalid time.
5861: .It Ar 14 X509_V_ERR_ERROR_IN_CERT_NOT_AFTER_FIELD: format error in certificate's notAfter field
5862: The certificate
5863: .Em notAfter
5864: field contains an invalid time.
5865: .It Ar 15 X509_V_ERR_ERROR_IN_CRL_LAST_UPDATE_FIELD: format error in CRL's lastUpdate field
5866: The CRL
5867: .Em lastUpdate
5868: field contains an invalid time.
5869: .It Ar 16 X509_V_ERR_ERROR_IN_CRL_NEXT_UPDATE_FIELD: format error in CRL's nextUpdate field
5870: The CRL
5871: .Em nextUpdate
5872: field contains an invalid time.
5873: .It Ar 17 X509_V_ERR_OUT_OF_MEM: out of memory
5874: An error occurred trying to allocate memory.
5875: This should never happen.
5876: .It Ar 18 X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate
5877: The passed certificate is self-signed and the same certificate cannot be
5878: found in the list of trusted certificates.
5879: .It Ar 19 X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain
5880: The certificate chain could be built up using the untrusted certificates but
5881: the root could not be found locally.
5882: .It Ar 20 X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY: unable to get local issuer certificate
5883: The issuer certificate of a locally looked up certificate could not be found.
5884: This normally means the list of trusted certificates is not complete.
5885: .It Ar 21 X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE: unable to verify the first certificate
5886: No signatures could be verified because the chain contains only one
5887: certificate and it is not self-signed.
5888: .It Ar 22 X509_V_ERR_CERT_CHAIN_TOO_LONG: certificate chain too long
5889: The certificate chain length is greater than the supplied maximum depth.
5890: Unused.
5891: .It Ar 23 X509_V_ERR_CERT_REVOKED: certificate revoked
5892: The certificate has been revoked.
5893: .It Ar 24 X509_V_ERR_INVALID_CA: invalid CA certificate
5894: A CA certificate is invalid.
5895: Either it is not a CA or its extensions are not consistent
5896: with the supplied purpose.
5897: .It Ar 25 X509_V_ERR_PATH_LENGTH_EXCEEDED: path length constraint exceeded
5898: The
5899: .Em basicConstraints
5900: pathlength parameter has been exceeded.
5901: .It Ar 26 X509_V_ERR_INVALID_PURPOSE: unsupported certificate purpose
5902: The supplied certificate cannot be used for the specified purpose.
5903: .It Ar 27 X509_V_ERR_CERT_UNTRUSTED: certificate not trusted
5904: The root CA is not marked as trusted for the specified purpose.
5905: .It Ar 28 X509_V_ERR_CERT_REJECTED: certificate rejected
5906: The root CA is marked to reject the specified purpose.
5907: .It Ar 29 X509_V_ERR_SUBJECT_ISSUER_MISMATCH: subject issuer mismatch
5908: The current candidate issuer certificate was rejected because its subject name
5909: did not match the issuer name of the current certificate.
5910: Only displayed when the
5911: .Fl issuer_checks
5912: option is set.
5913: .It Ar 30 X509_V_ERR_AKID_SKID_MISMATCH: authority and subject key identifier mismatch
5914: The current candidate issuer certificate was rejected because its subject key
5915: identifier was present and did not match the authority key identifier current
5916: certificate.
5917: Only displayed when the
5918: .Fl issuer_checks
5919: option is set.
5920: .It Ar 31 X509_V_ERR_AKID_ISSUER_SERIAL_MISMATCH: authority and issuer serial number mismatch
5921: The current candidate issuer certificate was rejected because its issuer name
5922: and serial number were present and did not match the authority key identifier
5923: of the current certificate.
5924: Only displayed when the
5925: .Fl issuer_checks
5926: option is set.
5927: .It Ar 32 X509_V_ERR_KEYUSAGE_NO_CERTSIGN:key usage does not include certificate signing
5928: The current candidate issuer certificate was rejected because its
5929: .Em keyUsage
5930: extension does not permit certificate signing.
5931: .It Ar 50 X509_V_ERR_APPLICATION_VERIFICATION: application verification failure
5932: An application specific error.
5933: Unused.
5934: .El
5935: .Sh VERIFY BUGS
5936: Although the issuer checks are a considerable improvement over the old
5937: technique, they still suffer from limitations in the underlying
5938: X509_LOOKUP API.
5939: One consequence of this is that trusted certificates with matching subject
5940: name must either appear in a file (as specified by the
5941: .Fl CAfile
5942: option) or a directory (as specified by
5943: .Fl CApath ) .
5944: If they occur in both, only the certificates in the file will
5945: be recognised.
5946: .Pp
5947: Previous versions of
5948: .Nm OpenSSL
5949: assumed certificates with matching subject name were identical and
5950: mishandled them.
5951: .\"
5952: .\" VERSION
5953: .\"
5954: .Sh VERSION
5955: .Nm openssl version
5956: .Op Fl abdfopv
5957: .Pp
5958: The
5959: .Nm version
5960: command is used to print out version information about
5961: .Nm OpenSSL .
5962: .Pp
5963: The options are as follows:
5964: .Bl -tag -width Ds
5965: .It Fl a
5966: All information: this is the same as setting all the other flags.
5967: .It Fl b
5968: The date the current version of
5969: .Nm OpenSSL
5970: was built.
5971: .It Fl d
5972: .Ev OPENSSLDIR
5973: setting.
5974: .It Fl f
5975: Compilation flags.
5976: .It Fl o
5977: Option information: various options set when the library was built.
5978: .It Fl p
5979: Platform setting.
5980: .It Fl v
5981: The current
5982: .Nm OpenSSL
5983: version.
5984: .El
5985: .Sh VERSION NOTES
5986: The output of
5987: .Nm openssl version -a
5988: would typically be used when sending in a bug report.
5989: .Sh VERSION HISTORY
5990: The
5991: .Fl d
5992: option was added in
5993: .Nm OpenSSL
5994: 0.9.7.
5995: .\"
5996: .\" X509
5997: .\"
5998: .Sh X509
5999: .nr nS 1
6000: .Nm "openssl x509"
6001: .Bk -words
6002: .Op Fl C
6003: .Op Fl addreject Ar arg
6004: .Op Fl addtrust Ar arg
6005: .Op Fl alias
6006: .Op Fl CA Ar file
6007: .Op Fl CAcreateserial
6008: .Op Fl CAform Ar DER | PEM
6009: .Op Fl CAkey Ar file
6010: .Op Fl CAkeyform Ar DER | PEM
6011: .Op Fl CAserial Ar file
6012: .Op Fl certopt Ar option
6013: .Op Fl checkend Ar arg
6014: .Op Fl clrext
6015: .Op Fl clrreject
6016: .Op Fl clrtrust
6017: .Op Fl dates
6018: .Op Fl days Ar arg
6019: .Op Fl email
6020: .Op Fl enddate
6021: .Op Fl extensions Ar section
6022: .Op Fl extfile Ar file
6023: .Op Fl fingerprint
6024: .Op Fl hash
6025: .Op Fl in Ar file
6026: .Op Fl inform Ar DER | NET | PEM
6027: .Op Fl issuer
6028: .Op Fl issuer_hash
6029: .Op Fl issuer_hash_old
6030: .Op Fl keyform Ar DER | PEM
1.29 bcook 6031: .Op Fl md5 | sha1
1.1 jsing 6032: .Op Fl modulus
6033: .Op Fl nameopt Ar option
6034: .Op Fl noout
6035: .Op Fl ocsp_uri
6036: .Op Fl ocspid
6037: .Op Fl out Ar file
6038: .Op Fl outform Ar DER | NET | PEM
6039: .Op Fl passin Ar arg
6040: .Op Fl pubkey
6041: .Op Fl purpose
6042: .Op Fl req
6043: .Op Fl serial
6044: .Op Fl set_serial Ar n
6045: .Op Fl setalias Ar arg
6046: .Op Fl signkey Ar file
6047: .Op Fl startdate
6048: .Op Fl subject
6049: .Op Fl subject_hash
6050: .Op Fl subject_hash_old
6051: .Op Fl text
6052: .Op Fl trustout
6053: .Op Fl x509toreq
6054: .Ek
6055: .nr nS 0
6056: .Pp
6057: The
6058: .Nm x509
6059: command is a multi-purpose certificate utility.
6060: It can be used to display certificate information, convert certificates to
6061: various forms, sign certificate requests like a
6062: .Qq mini CA ,
6063: or edit certificate trust settings.
6064: .Pp
6065: Since there are a large number of options, they are split up into
6066: various sections.
6067: .Sh X509 INPUT, OUTPUT, AND GENERAL PURPOSE OPTIONS
6068: .Bl -tag -width "XXXX"
6069: .It Fl in Ar file
6070: This specifies the input
6071: .Ar file
6072: to read a certificate from, or standard input if this option is not specified.
6073: .It Fl inform Ar DER | NET | PEM
6074: This specifies the input format.
6075: Normally, the command will expect an X.509 certificate,
6076: but this can change if other options such as
6077: .Fl req
6078: are present.
6079: The
6080: .Ar DER
6081: format is the DER encoding of the certificate and
6082: .Ar PEM
6083: is the base64 encoding of the DER encoding with header and footer lines added.
6084: The
6085: .Ar NET
6086: option is an obscure Netscape server format that is now
6087: obsolete.
1.29 bcook 6088: .It Fl md5 | sha1
1.1 jsing 6089: The digest to use.
6090: This affects any signing or display option that uses a message digest,
6091: such as the
6092: .Fl fingerprint , signkey ,
6093: and
6094: .Fl CA
6095: options.
6096: If not specified, MD5 is used.
6097: If the key being used to sign with is a DSA key,
6098: this option has no effect: SHA1 is always used with DSA keys.
6099: .It Fl out Ar file
6100: This specifies the output
6101: .Ar file
6102: to write to, or standard output by default.
6103: .It Fl outform Ar DER | NET | PEM
6104: This specifies the output format; the options have the same meaning as the
6105: .Fl inform
6106: option.
6107: .It Fl passin Ar arg
6108: The key password source.
6109: .El
6110: .Sh X509 DISPLAY OPTIONS
6111: .Sy Note :
6112: The
6113: .Fl alias
6114: and
6115: .Fl purpose
6116: options are also display options but are described in the
6117: .Sx X509 TRUST SETTINGS
6118: section.
6119: .Bl -tag -width "XXXX"
6120: .It Fl C
6121: This outputs the certificate in the form of a C source file.
6122: .It Fl certopt Ar option
6123: Customise the output format used with
6124: .Fl text .
6125: The
6126: .Ar option
6127: argument can be a single option or multiple options separated by commas.
6128: The
6129: .Fl certopt
6130: switch may also be used more than once to set multiple options.
6131: See the
6132: .Sx X509 TEXT OPTIONS
6133: section for more information.
6134: .It Fl dates
6135: Prints out the start and expiry dates of a certificate.
6136: .It Fl email
6137: Outputs the email address(es), if any.
6138: .It Fl enddate
6139: Prints out the expiry date of the certificate; that is, the
6140: .Em notAfter
6141: date.
6142: .It Fl fingerprint
6143: Prints out the digest of the DER-encoded version of the whole certificate
6144: (see
6145: .Sx DIGEST OPTIONS ) .
6146: .It Fl hash
6147: A synonym for
6148: .Fl subject_hash ,
6149: for backwards compatibility.
6150: .It Fl issuer
6151: Outputs the issuer name.
6152: .It Fl issuer_hash
6153: Outputs the
6154: .Qq hash
6155: of the certificate issuer name.
6156: .It Fl issuer_hash_old
6157: Outputs the
6158: .Qq hash
6159: of the certificate issuer name using the older algorithm
6160: as used by
6161: .Nm OpenSSL
6162: versions before 1.0.0.
6163: .It Fl modulus
6164: This option prints out the value of the modulus of the public key
6165: contained in the certificate.
6166: .It Fl nameopt Ar option
6167: Option which determines how the subject or issuer names are displayed.
6168: The
6169: .Ar option
6170: argument can be a single option or multiple options separated by commas.
6171: Alternatively, the
6172: .Fl nameopt
6173: switch may be used more than once to set multiple options.
6174: See the
6175: .Sx X509 NAME OPTIONS
6176: section for more information.
6177: .It Fl noout
6178: This option prevents output of the encoded version of the request.
6179: .It Fl ocsp_uri
6180: Outputs the OCSP responder addresses, if any.
6181: .It Fl ocspid
6182: Print OCSP hash values for the subject name and public key.
6183: .It Fl pubkey
6184: Output the public key.
6185: .It Fl serial
6186: Outputs the certificate serial number.
6187: .It Fl startdate
6188: Prints out the start date of the certificate; that is, the
6189: .Em notBefore
6190: date.
6191: .It Fl subject
6192: Outputs the subject name.
6193: .It Fl subject_hash
6194: Outputs the
6195: .Qq hash
6196: of the certificate subject name.
6197: This is used in
6198: .Nm OpenSSL
6199: to form an index to allow certificates in a directory to be looked up
6200: by subject name.
6201: .It Fl subject_hash_old
6202: Outputs the
6203: .Qq hash
6204: of the certificate subject name using the older algorithm
6205: as used by
6206: .Nm OpenSSL
6207: versions before 1.0.0.
6208: .It Fl text
6209: Prints out the certificate in text form.
6210: Full details are output including the public key, signature algorithms,
6211: issuer and subject names, serial number, any extensions present,
6212: and any trust settings.
6213: .El
6214: .Sh X509 TRUST SETTINGS
6215: Please note these options are currently experimental and may well change.
6216: .Pp
6217: A
6218: .Em trusted certificate
6219: is an ordinary certificate which has several
6220: additional pieces of information attached to it such as the permitted
6221: and prohibited uses of the certificate and an
6222: .Qq alias .
6223: .Pp
6224: Normally, when a certificate is being verified at least one certificate
6225: must be
6226: .Qq trusted .
6227: By default, a trusted certificate must be stored
6228: locally and must be a root CA: any certificate chain ending in this CA
6229: is then usable for any purpose.
6230: .Pp
6231: Trust settings currently are only used with a root CA.
6232: They allow a finer control over the purposes the root CA can be used for.
6233: For example, a CA may be trusted for an SSL client but not for
6234: SSL server use.
6235: .Pp
6236: See the description of the
6237: .Nm verify
6238: utility for more information on the meaning of trust settings.
6239: .Pp
6240: Future versions of
6241: .Nm OpenSSL
6242: will recognize trust settings on any certificate: not just root CAs.
6243: .Bl -tag -width "XXXX"
6244: .It Fl addreject Ar arg
6245: Adds a prohibited use.
6246: It accepts the same values as the
6247: .Fl addtrust
6248: option.
6249: .It Fl addtrust Ar arg
6250: Adds a trusted certificate use.
6251: Any object name can be used here, but currently only
6252: .Ar clientAuth
6253: .Pq SSL client use ,
6254: .Ar serverAuth
6255: .Pq SSL server use ,
6256: and
6257: .Ar emailProtection
6258: .Pq S/MIME email
6259: are used.
6260: Other
6261: .Nm OpenSSL
6262: applications may define additional uses.
6263: .It Fl alias
6264: Outputs the certificate alias, if any.
6265: .It Fl clrreject
6266: Clears all the prohibited or rejected uses of the certificate.
6267: .It Fl clrtrust
6268: Clears all the permitted or trusted uses of the certificate.
6269: .It Fl purpose
6270: This option performs tests on the certificate extensions and outputs
6271: the results.
6272: For a more complete description, see the
6273: .Sx X.509 CERTIFICATE EXTENSIONS
6274: section.
6275: .It Fl setalias Ar arg
6276: Sets the alias of the certificate.
6277: This will allow the certificate to be referred to using a nickname,
6278: for example
6279: .Qq Steve's Certificate .
6280: .It Fl trustout
6281: This causes
6282: .Nm x509
6283: to output a
6284: .Em trusted certificate .
6285: An ordinary or trusted certificate can be input, but by default an ordinary
6286: certificate is output and any trust settings are discarded.
6287: With the
6288: .Fl trustout
6289: option a trusted certificate is output.
6290: A trusted certificate is automatically output if any trust settings
6291: are modified.
6292: .El
6293: .Sh X509 SIGNING OPTIONS
6294: The
6295: .Nm x509
6296: utility can be used to sign certificates and requests: it
6297: can thus behave like a
6298: .Qq mini CA .
6299: .Bl -tag -width "XXXX"
6300: .It Fl CA Ar file
6301: Specifies the CA certificate to be used for signing.
6302: When this option is present,
6303: .Nm x509
6304: behaves like a
6305: .Qq mini CA .
6306: The input file is signed by the CA using this option;
6307: that is, its issuer name is set to the subject name of the CA and it is
6308: digitally signed using the CA's private key.
6309: .Pp
6310: This option is normally combined with the
6311: .Fl req
6312: option.
6313: Without the
6314: .Fl req
6315: option, the input is a certificate which must be self-signed.
6316: .It Fl CAcreateserial
6317: With this option the CA serial number file is created if it does not exist:
6318: it will contain the serial number
6319: .Sq 02
6320: and the certificate being signed will have
6321: .Sq 1
6322: as its serial number.
6323: Normally, if the
6324: .Fl CA
6325: option is specified and the serial number file does not exist, it is an error.
6326: .It Fl CAform Ar DER | PEM
6327: The format of the CA certificate file.
6328: The default is
6329: .Ar PEM .
6330: .It Fl CAkey Ar file
6331: Sets the CA private key to sign a certificate with.
6332: If this option is not specified, it is assumed that the CA private key
6333: is present in the CA certificate file.
6334: .It Fl CAkeyform Ar DER | PEM
6335: The format of the CA private key.
6336: The default is
6337: .Ar PEM .
6338: .It Fl CAserial Ar file
6339: Sets the CA serial number file to use.
6340: .Pp
6341: When the
6342: .Fl CA
6343: option is used to sign a certificate,
6344: it uses a serial number specified in a file.
6345: This file consists of one line containing an even number of hex digits
6346: with the serial number to use.
6347: After each use the serial number is incremented and written out
6348: to the file again.
6349: .Pp
6350: The default filename consists of the CA certificate file base name with
6351: .Pa .srl
6352: appended.
6353: For example, if the CA certificate file is called
6354: .Pa mycacert.pem ,
6355: it expects to find a serial number file called
6356: .Pa mycacert.srl .
6357: .It Fl checkend Ar arg
6358: Check whether the certificate expires in the next
6359: .Ar arg
6360: seconds.
6361: If so, exit with return value 1;
6362: otherwise exit with return value 0.
6363: .It Fl clrext
6364: Delete any extensions from a certificate.
6365: This option is used when a certificate is being created from another
6366: certificate (for example with the
6367: .Fl signkey
6368: or the
6369: .Fl CA
6370: options).
6371: Normally, all extensions are retained.
6372: .It Fl days Ar arg
6373: Specifies the number of days to make a certificate valid for.
6374: The default is 30 days.
6375: .It Fl extensions Ar section
6376: The section to add certificate extensions from.
6377: If this option is not specified, the extensions should either be
6378: contained in the unnamed
6379: .Pq default
6380: section or the default section should contain a variable called
6381: .Qq extensions
6382: which contains the section to use.
6383: .It Fl extfile Ar file
6384: File containing certificate extensions to use.
6385: If not specified, no extensions are added to the certificate.
6386: .It Fl keyform Ar DER | PEM
6387: Specifies the format
6388: .Pq DER or PEM
6389: of the private key file used in the
6390: .Fl signkey
6391: option.
6392: .It Fl req
6393: By default, a certificate is expected on input.
6394: With this option a certificate request is expected instead.
6395: .It Fl set_serial Ar n
6396: Specifies the serial number to use.
6397: This option can be used with either the
6398: .Fl signkey
6399: or
6400: .Fl CA
6401: options.
6402: If used in conjunction with the
6403: .Fl CA
6404: option, the serial number file (as specified by the
6405: .Fl CAserial
6406: or
6407: .Fl CAcreateserial
6408: options) is not used.
6409: .Pp
6410: The serial number can be decimal or hex (if preceded by
6411: .Sq 0x ) .
6412: Negative serial numbers can also be specified but their use is not recommended.
6413: .It Fl signkey Ar file
6414: This option causes the input file to be self-signed using the supplied
6415: private key.
6416: .Pp
6417: If the input file is a certificate, it sets the issuer name to the
6418: subject name
6419: .Pq i.e. makes it self-signed ,
6420: changes the public key to the supplied value,
6421: and changes the start and end dates.
6422: The start date is set to the current time and the end date is set to
6423: a value determined by the
6424: .Fl days
6425: option.
6426: Any certificate extensions are retained unless the
6427: .Fl clrext
6428: option is supplied.
6429: .Pp
6430: If the input is a certificate request, a self-signed certificate
6431: is created using the supplied private key using the subject name in
6432: the request.
6433: .It Fl x509toreq
6434: Converts a certificate into a certificate request.
6435: The
6436: .Fl signkey
6437: option is used to pass the required private key.
6438: .El
6439: .Sh X509 NAME OPTIONS
6440: The
6441: .Fl nameopt
6442: command line switch determines how the subject and issuer
6443: names are displayed.
6444: If no
6445: .Fl nameopt
6446: switch is present, the default
6447: .Qq oneline
6448: format is used which is compatible with previous versions of
6449: .Nm OpenSSL .
6450: Each option is described in detail below; all options can be preceded by a
6451: .Sq -
6452: to turn the option off.
6453: Only
6454: .Ar compat ,
6455: .Ar RFC2253 ,
6456: .Ar oneline ,
6457: and
6458: .Ar multiline
6459: will normally be used.
6460: .Bl -tag -width "XXXX"
6461: .It Ar align
6462: Align field values for a more readable output.
6463: Only usable with
6464: .Ar sep_multiline .
6465: .It Ar compat
6466: Use the old format.
6467: This is equivalent to specifying no name options at all.
6468: .It Ar dn_rev
6469: Reverse the fields of the DN.
6470: This is required by RFC 2253.
6471: As a side effect, this also reverses the order of multiple AVAs but this is
6472: permissible.
6473: .It Ar dump_all
6474: Dump all fields.
6475: This option, when used with
6476: .Ar dump_der ,
6477: allows the DER encoding of the structure to be unambiguously determined.
6478: .It Ar dump_der
6479: When this option is set, any fields that need to be hexdumped will
6480: be dumped using the DER encoding of the field.
6481: Otherwise just the content octets will be displayed.
6482: Both options use the RFC 2253 #XXXX... format.
6483: .It Ar dump_nostr
6484: Dump non-character string types
6485: .Pq for example OCTET STRING ;
6486: if this option is not set, non-character string types will be displayed
6487: as though each content octet represents a single character.
6488: .It Ar dump_unknown
6489: Dump any field whose OID is not recognised by
6490: .Nm OpenSSL .
6491: .It Ar esc_2253
6492: Escape the
6493: .Qq special
6494: characters required by RFC 2253 in a field that is
6495: .Dq \& ,+"\*(Lt\*(Gt; .
6496: Additionally,
6497: .Sq #
6498: is escaped at the beginning of a string
6499: and a space character at the beginning or end of a string.
6500: .It Ar esc_ctrl
6501: Escape control characters.
6502: That is, those with ASCII values less than 0x20
6503: .Pq space
6504: and the delete
6505: .Pq 0x7f
6506: character.
6507: They are escaped using the RFC 2253 \eXX notation (where XX are two hex
6508: digits representing the character value).
6509: .It Ar esc_msb
6510: Escape characters with the MSB set; that is, with ASCII values larger than
6511: 127.
6512: .It Ar multiline
6513: A multiline format.
6514: It is equivalent to
6515: .Ar esc_ctrl , esc_msb , sep_multiline ,
6516: .Ar space_eq , lname ,
6517: and
6518: .Ar align .
6519: .It Ar no_type
6520: This option does not attempt to interpret multibyte characters in any
6521: way.
6522: That is, their content octets are merely dumped as though one octet
6523: represents each character.
6524: This is useful for diagnostic purposes but will result in rather odd
6525: looking output.
6526: .It Ar nofname , sname , lname , oid
6527: These options alter how the field name is displayed.
6528: .Ar nofname
6529: does not display the field at all.
6530: .Ar sname
6531: uses the
6532: .Qq short name
6533: form (CN for
6534: .Ar commonName ,
6535: for example).
6536: .Ar lname
6537: uses the long form.
6538: .Ar oid
6539: represents the OID in numerical form and is useful for diagnostic purpose.
6540: .It Ar oneline
6541: A oneline format which is more readable than
6542: .Ar RFC2253 .
6543: It is equivalent to specifying the
6544: .Ar esc_2253 , esc_ctrl , esc_msb , utf8 ,
6545: .Ar dump_nostr , dump_der , use_quote , sep_comma_plus_spc ,
6546: .Ar space_eq ,
6547: and
6548: .Ar sname
6549: options.
6550: .It Ar RFC2253
6551: Displays names compatible with RFC 2253; equivalent to
6552: .Ar esc_2253 , esc_ctrl ,
6553: .Ar esc_msb , utf8 , dump_nostr , dump_unknown ,
6554: .Ar dump_der , sep_comma_plus , dn_rev ,
6555: and
6556: .Ar sname .
6557: .It Ar sep_comma_plus , sep_comma_plus_space , sep_semi_plus_space , sep_multiline
6558: These options determine the field separators.
6559: The first character is between RDNs and the second between multiple AVAs
6560: (multiple AVAs are very rare and their use is discouraged).
6561: The options ending in
6562: .Qq space
6563: additionally place a space after the separator to make it more readable.
6564: The
6565: .Ar sep_multiline
6566: uses a linefeed character for the RDN separator and a spaced
6567: .Sq +
6568: for the AVA separator.
6569: It also indents the fields by four characters.
6570: .It Ar show_type
6571: Show the type of the ASN1 character string.
6572: The type precedes the field contents.
6573: For example
6574: .Qq BMPSTRING: Hello World .
6575: .It Ar space_eq
6576: Places spaces round the
6577: .Sq =
6578: character which follows the field name.
6579: .It Ar use_quote
6580: Escapes some characters by surrounding the whole string with
6581: .Sq \&"
6582: characters.
6583: Without the option, all escaping is done with the
6584: .Sq \e
6585: character.
6586: .It Ar utf8
6587: Convert all strings to UTF8 format first.
6588: This is required by RFC 2253.
6589: If you are lucky enough to have a UTF8 compatible terminal,
6590: the use of this option (and
6591: .Em not
6592: setting
6593: .Ar esc_msb )
6594: may result in the correct display of multibyte
6595: .Pq international
6596: characters.
6597: If this option is not present, multibyte characters larger than 0xff
6598: will be represented using the format \eUXXXX for 16 bits and \eWXXXXXXXX
6599: for 32 bits.
6600: Also, if this option is off, any UTF8Strings will be converted to their
6601: character form first.
6602: .El
6603: .Sh X509 TEXT OPTIONS
6604: As well as customising the name output format, it is also possible to
6605: customise the actual fields printed using the
6606: .Fl certopt
6607: options when the
6608: .Fl text
6609: option is present.
6610: The default behaviour is to print all fields.
6611: .Bl -tag -width "XXXX"
6612: .It Ar ca_default
6613: The value used by the
6614: .Nm ca
6615: utility; equivalent to
6616: .Ar no_issuer , no_pubkey , no_header ,
6617: .Ar no_version , no_sigdump ,
6618: and
6619: .Ar no_signame .
6620: .It Ar compatible
6621: Use the old format.
6622: This is equivalent to specifying no output options at all.
6623: .It Ar ext_default
6624: Retain default extension behaviour: attempt to print out unsupported
6625: certificate extensions.
6626: .It Ar ext_dump
6627: Hex dump unsupported extensions.
6628: .It Ar ext_error
6629: Print an error message for unsupported certificate extensions.
6630: .It Ar ext_parse
6631: ASN1 parse unsupported extensions.
6632: .It Ar no_aux
6633: Don't print out certificate trust information.
6634: .It Ar no_extensions
6635: Don't print out any X509V3 extensions.
6636: .It Ar no_header
6637: Don't print header information: that is, the lines saying
6638: .Qq Certificate
6639: and
6640: .Qq Data .
6641: .It Ar no_issuer
6642: Don't print out the issuer name.
6643: .It Ar no_pubkey
6644: Don't print out the public key.
6645: .It Ar no_serial
6646: Don't print out the serial number.
6647: .It Ar no_sigdump
6648: Don't give a hexadecimal dump of the certificate signature.
6649: .It Ar no_signame
6650: Don't print out the signature algorithm used.
6651: .It Ar no_subject
6652: Don't print out the subject name.
6653: .It Ar no_validity
6654: Don't print the validity; that is, the
6655: .Em notBefore
6656: and
6657: .Em notAfter
6658: fields.
6659: .It Ar no_version
6660: Don't print out the version number.
6661: .El
6662: .Sh X509 EXAMPLES
6663: Display the contents of a certificate:
6664: .Pp
6665: .Dl $ openssl x509 -in cert.pem -noout -text
6666: .Pp
6667: Display the certificate serial number:
6668: .Pp
6669: .Dl $ openssl x509 -in cert.pem -noout -serial
6670: .Pp
6671: Display the certificate subject name:
6672: .Pp
6673: .Dl $ openssl x509 -in cert.pem -noout -subject
6674: .Pp
6675: Display the certificate subject name in RFC 2253 form:
6676: .Pp
6677: .Dl $ openssl x509 -in cert.pem -noout -subject -nameopt RFC2253
6678: .Pp
6679: Display the certificate subject name in oneline form on a terminal
6680: supporting UTF8:
6681: .Bd -literal -offset indent
6682: $ openssl x509 -in cert.pem -noout -subject \e
6683: -nameopt oneline,-esc_msb
6684: .Ed
6685: .Pp
6686: Display the certificate MD5 fingerprint:
6687: .Pp
6688: .Dl $ openssl x509 -in cert.pem -noout -fingerprint
6689: .Pp
6690: Display the certificate SHA1 fingerprint:
6691: .Pp
6692: .Dl $ openssl x509 -sha1 -in cert.pem -noout -fingerprint
6693: .Pp
6694: Convert a certificate from PEM to DER format:
6695: .Pp
6696: .Dl "$ openssl x509 -in cert.pem -inform PEM -out cert.der -outform DER"
6697: .Pp
6698: Convert a certificate to a certificate request:
6699: .Bd -literal -offset indent
6700: $ openssl x509 -x509toreq -in cert.pem -out req.pem \e
6701: -signkey key.pem
6702: .Ed
6703: .Pp
6704: Convert a certificate request into a self-signed certificate using
6705: extensions for a CA:
6706: .Bd -literal -offset indent
6707: $ openssl x509 -req -in careq.pem -extfile openssl.cnf -extensions \e
6708: v3_ca -signkey key.pem -out cacert.pem
6709: .Ed
6710: .Pp
6711: Sign a certificate request using the CA certificate above and add user
6712: certificate extensions:
6713: .Bd -literal -offset indent
6714: $ openssl x509 -req -in req.pem -extfile openssl.cnf -extensions \e
6715: v3_usr -CA cacert.pem -CAkey key.pem -CAcreateserial
6716: .Ed
6717: .Pp
6718: Set a certificate to be trusted for SSL
6719: client use and set its alias to
6720: .Qq Steve's Class 1 CA :
6721: .Bd -literal -offset indent
6722: $ openssl x509 -in cert.pem -addtrust clientAuth \e
6723: -setalias "Steve's Class 1 CA" -out trust.pem
6724: .Ed
6725: .Sh X509 NOTES
6726: The PEM format uses the header and footer lines:
6727: .Bd -unfilled -offset indent
6728: -----BEGIN CERTIFICATE-----
6729: -----END CERTIFICATE-----
6730: .Ed
6731: .Pp
6732: It will also handle files containing:
6733: .Bd -unfilled -offset indent
6734: -----BEGIN X509 CERTIFICATE-----
6735: -----END X509 CERTIFICATE-----
6736: .Ed
6737: .Pp
6738: Trusted certificates have the lines:
6739: .Bd -unfilled -offset indent
6740: -----BEGIN TRUSTED CERTIFICATE-----
6741: -----END TRUSTED CERTIFICATE-----
6742: .Ed
6743: .Pp
6744: The conversion to UTF8 format used with the name options assumes that
6745: T61Strings use the ISO 8859-1 character set.
6746: This is wrong, but Netscape and MSIE do this, as do many certificates.
6747: So although this is incorrect
6748: it is more likely to display the majority of certificates correctly.
6749: .Pp
6750: The
6751: .Fl fingerprint
6752: option takes the digest of the DER-encoded certificate.
6753: This is commonly called a
6754: .Qq fingerprint .
6755: Because of the nature of message digests, the fingerprint of a certificate
6756: is unique to that certificate and two certificates with the same fingerprint
6757: can be considered to be the same.
6758: .Pp
6759: The Netscape fingerprint uses MD5, whereas MSIE uses SHA1.
6760: .Pp
6761: The
6762: .Fl email
6763: option searches the subject name and the subject alternative
6764: name extension.
6765: Only unique email addresses will be printed out: it will
6766: not print the same address more than once.
6767: .Sh X.509 CERTIFICATE EXTENSIONS
6768: The
6769: .Fl purpose
6770: option checks the certificate extensions and determines
6771: what the certificate can be used for.
6772: The actual checks done are rather
6773: complex and include various hacks and workarounds to handle broken
6774: certificates and software.
6775: .Pp
6776: The same code is used when verifying untrusted certificates in chains,
6777: so this section is useful if a chain is rejected by the verify code.
6778: .Pp
6779: The
6780: .Em basicConstraints
6781: extension CA flag is used to determine whether the
6782: certificate can be used as a CA.
6783: If the CA flag is true, it is a CA;
6784: if the CA flag is false, it is not a CA.
6785: .Em All
6786: CAs should have the CA flag set to true.
6787: .Pp
6788: If the
6789: .Em basicConstraints
6790: extension is absent, then the certificate is
6791: considered to be a
6792: .Qq possible CA ;
6793: other extensions are checked according to the intended use of the certificate.
6794: A warning is given in this case because the certificate should really not
6795: be regarded as a CA: however,
6796: it is allowed to be a CA to work around some broken software.
6797: .Pp
6798: If the certificate is a V1 certificate
6799: .Pq and thus has no extensions
6800: and it is self-signed, it is also assumed to be a CA but a warning is again
6801: given: this is to work around the problem of Verisign roots which are V1
6802: self-signed certificates.
6803: .Pp
6804: If the
6805: .Em keyUsage
6806: extension is present, then additional restraints are
6807: made on the uses of the certificate.
6808: A CA certificate
6809: .Em must
6810: have the
6811: .Em keyCertSign
6812: bit set if the
6813: .Em keyUsage
6814: extension is present.
6815: .Pp
6816: The extended key usage extension places additional restrictions on the
6817: certificate uses.
6818: If this extension is present
6819: .Pq whether critical or not ,
6820: the key can only be used for the purposes specified.
6821: .Pp
6822: A complete description of each test is given below.
6823: The comments about
6824: .Em basicConstraints
6825: and
6826: .Em keyUsage
6827: and V1 certificates above apply to
6828: .Em all
6829: CA certificates.
6830: .Bl -tag -width "XXXX"
6831: .It Ar SSL Client
6832: The extended key usage extension must be absent or include the
6833: .Qq web client authentication
6834: OID.
6835: .Ar keyUsage
6836: must be absent or it must have the
6837: .Em digitalSignature
6838: bit set.
6839: Netscape certificate type must be absent or it must have the SSL
6840: client bit set.
6841: .It Ar SSL Client CA
6842: The extended key usage extension must be absent or include the
6843: .Qq web client authentication
6844: OID.
6845: Netscape certificate type must be absent or it must have the SSL CA
6846: bit set: this is used as a work around if the
6847: .Em basicConstraints
6848: extension is absent.
6849: .It Ar SSL Server
6850: The extended key usage extension must be absent or include the
6851: .Qq web server authentication
6852: and/or one of the SGC OIDs.
6853: .Em keyUsage
6854: must be absent or it must have the
6855: .Em digitalSignature
6856: set, the
6857: .Em keyEncipherment
6858: set, or both bits set.
6859: Netscape certificate type must be absent or have the SSL server bit set.
6860: .It Ar SSL Server CA
6861: The extended key usage extension must be absent or include the
6862: .Qq web server authentication
6863: and/or one of the SGC OIDs.
6864: Netscape certificate type must be absent or the SSL CA
6865: bit must be set: this is used as a work around if the
6866: .Em basicConstraints
6867: extension is absent.
6868: .It Ar Netscape SSL Server
6869: For Netscape SSL clients to connect to an SSL server; it must have the
6870: .Em keyEncipherment
6871: bit set if the
6872: .Em keyUsage
6873: extension is present.
6874: This isn't always valid because some cipher suites use the key for
6875: digital signing.
6876: Otherwise it is the same as a normal SSL server.
6877: .It Ar Common S/MIME Client Tests
6878: The extended key usage extension must be absent or include the
6879: .Qq email protection
6880: OID.
6881: Netscape certificate type must be absent or should have the
6882: .Em S/MIME
6883: bit set.
6884: If the
6885: .Em S/MIME
6886: bit is not set in Netscape certificate type, then the SSL
6887: client bit is tolerated as an alternative but a warning is shown:
6888: this is because some Verisign certificates don't set the
6889: .Em S/MIME
6890: bit.
6891: .It Ar S/MIME Signing
6892: In addition to the common
6893: .Em S/MIME
6894: client tests, the
6895: .Em digitalSignature
6896: bit must be set if the
6897: .Em keyUsage
6898: extension is present.
6899: .It Ar S/MIME Encryption
6900: In addition to the common
6901: .Em S/MIME
6902: tests, the
6903: .Em keyEncipherment
6904: bit must be set if the
6905: .Em keyUsage
6906: extension is present.
6907: .It Ar S/MIME CA
6908: The extended key usage extension must be absent or include the
6909: .Qq email protection
6910: OID.
6911: Netscape certificate type must be absent or must have the
6912: .Em S/MIME CA
6913: bit set: this is used as a work around if the
6914: .Em basicConstraints
6915: extension is absent.
6916: .It Ar CRL Signing
6917: The
6918: .Em keyUsage
6919: extension must be absent or it must have the
6920: .Em CRL
6921: signing bit set.
6922: .It Ar CRL Signing CA
6923: The normal CA tests apply.
6924: Except in this case the
6925: .Em basicConstraints
6926: extension must be present.
6927: .El
6928: .Sh X509 BUGS
6929: Extensions in certificates are not transferred to certificate requests and
6930: vice versa.
6931: .Pp
6932: It is possible to produce invalid certificates or requests by specifying the
6933: wrong private key or using inconsistent options in some cases: these should
6934: be checked.
6935: .Pp
6936: There should be options to explicitly set such things as start and end dates,
6937: rather than an offset from the current time.
6938: .Pp
6939: The code to implement the verify behaviour described in the
6940: .Sx X509 TRUST SETTINGS
6941: is currently being developed.
6942: It thus describes the intended behaviour rather than the current behaviour.
6943: It is hoped that it will represent reality in
6944: .Nm OpenSSL
6945: 0.9.5 and later.
6946: .Sh X509 HISTORY
6947: Before
6948: .Nm OpenSSL
6949: 0.9.8,
6950: the default digest for RSA keys was MD5.
6951: .Pp
6952: The hash algorithm used in the
6953: .Fl subject_hash
6954: and
6955: .Fl issuer_hash
6956: options before
6957: .Nm OpenSSL
6958: 1.0.0 was based on the deprecated MD5 algorithm and the encoding
6959: of the distinguished name.
6960: In
6961: .Nm OpenSSL
6962: 1.0.0 and later it is based on a canonical version of the DN using SHA1.
6963: This means that any directories using the old form
6964: must have their links rebuilt using
6965: .Ar c_rehash
6966: or similar.
1.38 jmc 6967: .Sh COMMON NOTATION
6968: Several commands share a common syntax,
6969: as detailed below.
6970: .Pp
6971: Password arguments, typically specified using
1.33 jmc 6972: .Fl passin
6973: and
6974: .Fl passout
1.38 jmc 6975: for input and output passwords,
6976: allow passwords to be obtained from a variety of sources.
6977: Both of these options take a single argument, described below.
1.33 jmc 6978: If no password argument is given and a password is required,
6979: then the user is prompted to enter one:
6980: this will typically be read from the current terminal with echoing turned off.
1.38 jmc 6981: .Bl -tag -width "pass:password" -offset indent
6982: .It Cm pass : Ns Ar password
1.33 jmc 6983: The actual password is
6984: .Ar password .
1.38 jmc 6985: Since the password is visible to utilities,
1.33 jmc 6986: this form should only be used where security is not important.
1.38 jmc 6987: .It Cm env : Ns Ar var
1.33 jmc 6988: Obtain the password from the environment variable
6989: .Ar var .
1.38 jmc 6990: Since the environment of other processes is visible,
6991: this option should be used with caution.
6992: .It Cm file : Ns Ar path
1.33 jmc 6993: The first line of
6994: .Ar path
6995: is the password.
6996: If the same
6997: .Ar path
6998: argument is supplied to
6999: .Fl passin
7000: and
7001: .Fl passout ,
7002: then the first line will be used for the input password and the next line
7003: for the output password.
7004: .Ar path
7005: need not refer to a regular file:
7006: it could, for example, refer to a device or named pipe.
1.38 jmc 7007: .It Cm fd : Ns Ar number
1.33 jmc 7008: Read the password from the file descriptor
7009: .Ar number .
1.38 jmc 7010: This can be used to send the data via a pipe, for example.
7011: .It Cm stdin
1.33 jmc 7012: Read the password from standard input.
1.35 jmc 7013: .El
1.38 jmc 7014: .Pp
1.64 jmc 7015: Input/output formats,
1.38 jmc 7016: typically specified using
7017: .Fl inform
7018: and
7019: .Fl outform ,
1.64 jmc 7020: indicate the format being read from or written to.
1.38 jmc 7021: The argument is case insensitive.
7022: .Pp
7023: .Bl -tag -width Ds -offset indent -compact
7024: .It Cm der
7025: Distinguished Encoding Rules (DER)
7026: is a binary format.
1.64 jmc 7027: .It Cm net
7028: Insecure legacy format.
1.38 jmc 7029: .It Cm pem
7030: Privacy Enhanced Mail (PEM)
7031: is base64-encoded.
7032: .It Cm txt
7033: Plain ASCII text.
7034: .El
1.35 jmc 7035: .Sh ENVIRONMENT
7036: The following environment variables affect the execution of
7037: .Nm openssl :
1.38 jmc 7038: .Bl -tag -width "/etc/ssl/openssl.cnf"
1.35 jmc 7039: .It Ev OPENSSL_CONF
7040: The location of the master configuration file.
1.33 jmc 7041: .El
1.1 jsing 7042: .\"
7043: .\" FILES
7044: .\"
7045: .Sh FILES
7046: .Bl -tag -width "/etc/ssl/openssl.cnf" -compact
1.17 sobrado 7047: .It Pa /etc/ssl/
1.1 jsing 7048: Default config directory for
7049: .Nm openssl .
1.17 sobrado 7050: .It Pa /etc/ssl/lib/
1.1 jsing 7051: Unused.
1.17 sobrado 7052: .It Pa /etc/ssl/private/
1.1 jsing 7053: Default private key directory.
1.17 sobrado 7054: .It Pa /etc/ssl/openssl.cnf
1.1 jsing 7055: Default configuration file for
7056: .Nm openssl .
1.17 sobrado 7057: .It Pa /etc/ssl/x509v3.cnf
1.1 jsing 7058: Default configuration file for
7059: .Nm x509
7060: certificates.
7061: .El
7062: .\"
7063: .\" SEE ALSO
7064: .\"
7065: .Sh SEE ALSO
1.26 jmc 7066: .Xr nc 1 ,
1.1 jsing 7067: .Xr ssl 8 ,
7068: .Xr starttls 8
7069: .Sh STANDARDS
7070: .Rs
7071: .%D February 1995
7072: .%Q Netscape Communications Corp.
7073: .%T The SSL Protocol
7074: .Re
7075: .Pp
7076: .Rs
7077: .%D November 1996
7078: .%Q Netscape Communications Corp.
7079: .%T The SSL 3.0 Protocol
7080: .Re
7081: .Pp
7082: .Rs
7083: .%A T. Dierks
7084: .%A C. Allen
7085: .%D January 1999
7086: .%R RFC 2246
7087: .%T The TLS Protocol Version 1.0
7088: .Re
7089: .Pp
7090: .Rs
7091: .%A M. Wahl
7092: .%A S. Killie
7093: .%A T. Howes
7094: .%D December 1997
7095: .%R RFC 2253
7096: .%T Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
7097: .Re
7098: .Pp
7099: .Rs
7100: .%A B. Kaliski
7101: .%D March 1998
7102: .%R RFC 2315
7103: .%T PKCS #7: Cryptographic Message Syntax Version 1.5
7104: .Re
7105: .Pp
7106: .Rs
7107: .%A R. Housley
7108: .%A W. Ford
7109: .%A W. Polk
7110: .%A D. Solo
7111: .%D January 1999
7112: .%R RFC 2459
7113: .%T Internet X.509 Public Key Infrastructure Certificate and CRL Profile
7114: .Re
7115: .Pp
7116: .Rs
7117: .%A M. Myers
7118: .%A R. Ankney
7119: .%A A. Malpani
7120: .%A S. Galperin
7121: .%A C. Adams
7122: .%D June 1999
7123: .%R RFC 2560
7124: .%T X.509 Internet Public Key Infrastructure Online Certificate Status Protocol \(en OCSP
7125: .Re
7126: .Pp
7127: .Rs
7128: .%A R. Housley
7129: .%D June 1999
7130: .%R RFC 2630
7131: .%T Cryptographic Message Syntax
7132: .Re
7133: .Pp
7134: .Rs
7135: .%A P. Chown
7136: .%D June 2002
7137: .%R RFC 3268
1.24 jmc 7138: .%T Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)
1.1 jsing 7139: .Re