4 {- join("\n", @autowarntext) -}
10 openssl-ts - Time Stamping Authority tool (client/server)
16 [B<-config> I<configfile>]
17 [B<-data> I<file_to_hash>]
18 [B<-digest> I<digest_bytes>]
20 [B<-tspolicy> I<object_id>]
23 [B<-in> I<request.tsq>]
24 [B<-out> I<request.tsq>]
26 {- $OpenSSL::safe::opt_r_synopsis -}
30 [B<-config> I<configfile>]
31 [B<-section> I<tsa_section>]
32 [B<-queryfile> I<request.tsq>]
33 [B<-passin> I<password_src>]
34 [B<-signer> I<tsa_cert.pem>]
35 [B<-inkey> I<file_or_id>]
37 [B<-chain> I<certs_file.pem>]
38 [B<-tspolicy> I<object_id>]
39 [B<-in> I<response.tsr>]
41 [B<-out> I<response.tsr>]
48 [B<-data> I<file_to_hash>]
49 [B<-digest> I<digest_bytes>]
50 [B<-queryfile> I<request.tsq>]
51 [B<-in> I<response.tsr>]
53 [B<-CApath> I<trusted_cert_path>]
54 [B<-CAfile> I<trusted_certs.pem>]
55 [B<-untrusted> I<cert_file.pem>]
59 [B<-attime> I<timestamp>]
75 [B<-purpose> I<purpose>]
81 [B<-auth_level> I<num>]
82 [B<-verify_depth> I<num>]
83 [B<-verify_email> I<email>]
84 [B<-verify_hostname> I<hostname>]
86 [B<-verify_name> I<name>]
89 =for openssl ifdef engine
93 This command is a basic Time Stamping Authority (TSA) client and
94 server application as specified in RFC 3161 (Time-Stamp Protocol, TSP). A
95 TSA can be part of a PKI deployment and its role is to provide long
96 term proof of the existence of a certain datum before a particular
97 time. Here is a brief description of the protocol:
103 The TSA client computes a one-way hash value for a data file and sends
108 The TSA attaches the current date and time to the received hash value,
109 signs them and sends the timestamp token back to the client. By
110 creating this token the TSA certifies the existence of the original
111 data file at the time of response generation.
115 The TSA client receives the timestamp token and verifies the
116 signature on it. It also checks if the token contains the same hash
117 value that it had sent to the TSA.
121 There is one DER encoded protocol data unit defined for transporting a time
122 stamp request to the TSA and one for sending the timestamp response
123 back to the client. This command has three main functions:
124 creating a timestamp request based on a data file,
125 creating a timestamp response based on a request, verifying if a
126 response corresponds to a particular request or a data file.
128 There is no support for sending the requests/responses automatically
129 over HTTP or TCP yet as suggested in RFC 3161. The users must send the
130 requests either by ftp or e-mail.
134 =head2 Timestamp Request generation
136 The B<-query> switch can be used for creating and printing a timestamp
137 request with the following options:
141 =item B<-config> I<configfile>
143 The configuration file to use.
144 Optional; for a description of the default value,
145 see L<openssl(1)/COMMAND SUMMARY>.
147 =item B<-data> I<file_to_hash>
149 The data file for which the timestamp request needs to be
150 created. stdin is the default if neither the B<-data> nor the B<-digest>
151 parameter is specified. (Optional)
153 =item B<-digest> I<digest_bytes>
155 It is possible to specify the message imprint explicitly without the data
156 file. The imprint must be specified in a hexadecimal format, two characters
157 per byte, the bytes optionally separated by colons (e.g. 1A:F6:01:... or
158 1AF601...). The number of bytes must match the message digest algorithm
163 The message digest to apply to the data file.
164 Any digest supported by the L<openssl-dgst(1)> command can be used.
165 The default is SHA-256. (Optional)
167 =item B<-tspolicy> I<object_id>
169 The policy that the client expects the TSA to use for creating the
170 timestamp token. Either the dotted OID notation or OID names defined
171 in the config file can be used. If no policy is requested the TSA will
172 use its own default policy. (Optional)
176 No nonce is specified in the request if this option is
177 given. Otherwise a 64 bit long pseudo-random none is
178 included in the request. It is recommended to use nonce to
179 protect against replay-attacks. (Optional)
183 The TSA is expected to include its signing certificate in the
186 =item B<-in> I<request.tsq>
188 This option specifies a previously created timestamp request in DER
189 format that will be printed into the output file. Useful when you need
190 to examine the content of a request in human-readable
193 =item B<-out> I<request.tsq>
195 Name of the output file to which the request will be written. Default
196 is stdout. (Optional)
200 If this option is specified the output is human-readable text format
201 instead of DER. (Optional)
203 {- $OpenSSL::safe::opt_r_item -}
207 =head2 Timestamp Response generation
209 A timestamp response (TimeStampResp) consists of a response status
210 and the timestamp token itself (ContentInfo), if the token generation was
211 successful. The B<-reply> command is for creating a timestamp
212 response or timestamp token based on a request and printing the
213 response/token in human-readable format. If B<-token_out> is not
214 specified the output is always a timestamp response (TimeStampResp),
215 otherwise it is a timestamp token (ContentInfo).
219 =item B<-config> I<configfile>
221 The configuration file to use.
222 Optional; for a description of the default value,
223 see L<openssl(1)/COMMAND SUMMARY>.
224 See L</CONFIGURATION FILE OPTIONS> for configurable variables.
226 =item B<-section> I<tsa_section>
228 The name of the config file section containing the settings for the
229 response generation. If not specified the default TSA section is
230 used, see L</CONFIGURATION FILE OPTIONS> for details. (Optional)
232 =item B<-queryfile> I<request.tsq>
234 The name of the file containing a DER encoded timestamp request. (Optional)
236 =item B<-passin> I<password_src>
238 Specifies the password source for the private key of the TSA. See
239 description in L<openssl(1)>. (Optional)
241 =item B<-signer> I<tsa_cert.pem>
243 The signer certificate of the TSA in PEM format. The TSA signing
244 certificate must have exactly one extended key usage assigned to it:
245 timeStamping. The extended key usage must also be critical, otherwise
246 the certificate is going to be refused. Overrides the B<signer_cert>
247 variable of the config file. (Optional)
249 =item B<-inkey> I<file_or_id>
251 The signer private key of the TSA in PEM format. Overrides the
252 B<signer_key> config file option. (Optional)
253 If no engine is used, the argument is taken as a file; if an engine is
254 specified, the argument is given to the engine as a key identifier.
258 Signing digest to use. Overrides the B<signer_digest> config file
259 option. (Mandatory unless specified in the config file)
261 =item B<-chain> I<certs_file.pem>
263 The collection of certificates in PEM format that will all
264 be included in the response in addition to the signer certificate if
265 the B<-cert> option was used for the request. This file is supposed to
266 contain the certificate chain for the signer certificate from its
267 issuer upwards. The B<-reply> command does not build a certificate
268 chain automatically. (Optional)
270 =item B<-tspolicy> I<object_id>
272 The default policy to use for the response unless the client
273 explicitly requires a particular TSA policy. The OID can be specified
274 either in dotted notation or with its name. Overrides the
275 B<default_policy> config file option. (Optional)
277 =item B<-in> I<response.tsr>
279 Specifies a previously created timestamp response or timestamp token
280 (if B<-token_in> is also specified) in DER format that will be written
281 to the output file. This option does not require a request, it is
282 useful e.g. when you need to examine the content of a response or
283 token or you want to extract the timestamp token from a response. If
284 the input is a token and the output is a timestamp response a default
285 'granted' status info is added to the token. (Optional)
289 This flag can be used together with the B<-in> option and indicates
290 that the input is a DER encoded timestamp token (ContentInfo) instead
291 of a timestamp response (TimeStampResp). (Optional)
293 =item B<-out> I<response.tsr>
295 The response is written to this file. The format and content of the
296 file depends on other options (see B<-text>, B<-token_out>). The default is
301 The output is a timestamp token (ContentInfo) instead of timestamp
302 response (TimeStampResp). (Optional)
306 If this option is specified the output is human-readable text format
307 instead of DER. (Optional)
309 =item B<-engine> I<id>
311 Specifying an engine (by its unique I<id> string) will cause this command
312 to attempt to obtain a functional reference to the specified engine,
313 thus initialising it if needed. The engine will then be set as the default
314 for all available algorithms. Default is built-in. (Optional)
318 =head2 Timestamp Response verification
320 The B<-verify> command is for verifying if a timestamp response or time
321 stamp token is valid and matches a particular timestamp request or
322 data file. The B<-verify> command does not use the configuration file.
326 =item B<-data> I<file_to_hash>
328 The response or token must be verified against file_to_hash. The file
329 is hashed with the message digest algorithm specified in the token.
330 The B<-digest> and B<-queryfile> options must not be specified with this one.
333 =item B<-digest> I<digest_bytes>
335 The response or token must be verified against the message digest specified
336 with this option. The number of bytes must match the message digest algorithm
337 specified in the token. The B<-data> and B<-queryfile> options must not be
338 specified with this one. (Optional)
340 =item B<-queryfile> I<request.tsq>
342 The original timestamp request in DER format. The B<-data> and B<-digest>
343 options must not be specified with this one. (Optional)
345 =item B<-in> I<response.tsr>
347 The timestamp response that needs to be verified in DER format. (Mandatory)
351 This flag can be used together with the B<-in> option and indicates
352 that the input is a DER encoded timestamp token (ContentInfo) instead
353 of a timestamp response (TimeStampResp). (Optional)
355 =item B<-CAfile> I<file>, B<-CApath> I<dir>
357 See L<openssl(1)/Trusted Certificate Options> for more information.
359 =item B<-untrusted> I<cert_file.pem>
361 Set of additional untrusted certificates in PEM format which may be
362 needed when building the certificate chain for the TSA's signing
363 certificate. This file must contain the TSA signing certificate and
364 all intermediate CA certificates unless the response includes them.
367 =item I<verify options>
369 The options B<-attime>, B<-check_ss_sig>, B<-crl_check>,
370 B<-crl_check_all>, B<-explicit_policy>, B<-extended_crl>, B<-ignore_critical>,
371 B<-inhibit_any>, B<-inhibit_map>, B<-issuer_checks>, B<-no_alt_chains>,
372 B<-no_check_time>, B<-partial_chain>, B<-policy>, B<-policy_check>,
373 B<-policy_print>, B<-purpose>, B<-suiteB_128>, B<-suiteB_128_only>,
374 B<-suiteB_192>, B<-trusted_first>, B<-use_deltas>, B<-auth_level>,
375 B<-verify_depth>, B<-verify_email>, B<-verify_hostname>, B<-verify_ip>,
376 B<-verify_name>, and B<-x509_strict> can be used to control timestamp
377 verification. See L<openssl-verify(1)>.
381 =head1 CONFIGURATION FILE OPTIONS
383 The B<-query> and B<-reply> commands make use of a configuration file.
385 for a general description of the syntax of the config file. The
386 B<-query> command uses only the symbolic OID names section
387 and it can work without it. However, the B<-reply> command needs the
388 config file for its operation.
390 When there is a command line switch equivalent of a variable the
391 switch always overrides the settings in the config file.
395 =item B<tsa> section, B<default_tsa>
397 This is the main section and it specifies the name of another section
398 that contains all the options for the B<-reply> command. This default
399 section can be overridden with the B<-section> command line switch. (Optional)
403 See L<openssl-ca(1)> for description. (Optional)
407 See L<openssl-ca(1)> for description. (Optional)
411 See L<openssl-ca(1)> for description. (Optional)
415 The name of the file containing the hexadecimal serial number of the
416 last timestamp response created. This number is incremented by 1 for
417 each response. If the file does not exist at the time of response
418 generation a new file is created with serial number 1. (Mandatory)
420 =item B<crypto_device>
422 Specifies the OpenSSL engine that will be set as the default for
423 all available algorithms. The default value is built-in, you can specify
424 any other engines supported by OpenSSL (e.g. use chil for the NCipher HSM).
429 TSA signing certificate in PEM format. The same as the B<-signer>
430 command line option. (Optional)
434 A file containing a set of PEM encoded certificates that need to be
435 included in the response. The same as the B<-chain> command line
440 The private key of the TSA in PEM format. The same as the B<-inkey>
441 command line option. (Optional)
443 =item B<signer_digest>
445 Signing digest to use. The same as the
446 B<-I<digest>> command line option. (Mandatory unless specified on the command
449 =item B<default_policy>
451 The default policy to use when the request does not mandate any
452 policy. The same as the B<-tspolicy> command line option. (Optional)
454 =item B<other_policies>
456 Comma separated list of policies that are also acceptable by the TSA
457 and used only if the request explicitly specifies one of them. (Optional)
461 The list of message digest algorithms that the TSA accepts. At least
462 one algorithm must be specified. (Mandatory)
466 The accuracy of the time source of the TSA in seconds, milliseconds
467 and microseconds. E.g. secs:1, millisecs:500, microsecs:100. If any of
468 the components is missing zero is assumed for that field. (Optional)
470 =item B<clock_precision_digits>
472 Specifies the maximum number of digits, which represent the fraction of
473 seconds, that need to be included in the time field. The trailing zeros
474 must be removed from the time, so there might actually be fewer digits,
475 or no fraction of seconds at all. Supported only on UNIX platforms.
476 The maximum value is 6, default is 0.
481 If this option is yes the responses generated by this TSA can always
482 be ordered, even if the time difference between two responses is less
483 than the sum of their accuracies. Default is no. (Optional)
487 Set this option to yes if the subject name of the TSA must be included in
488 the TSA name field of the response. Default is no. (Optional)
490 =item B<ess_cert_id_chain>
492 The SignedData objects created by the TSA always contain the
493 certificate identifier of the signing certificate in a signed
494 attribute (see RFC 2634, Enhanced Security Services). If this option
495 is set to yes and either the B<certs> variable or the B<-chain> option
496 is specified then the certificate identifiers of the chain will also
497 be included in the SigningCertificate signed attribute. If this
498 variable is set to no, only the signing certificate identifier is
499 included. Default is no. (Optional)
501 =item B<ess_cert_id_alg>
503 This option specifies the hash function to be used to calculate the TSA's
504 public key certificate identifier. Default is sha256. (Optional)
510 All the examples below presume that B<OPENSSL_CONF> is set to a proper
511 configuration file, e.g. the example configuration file
512 F<openssl/apps/openssl.cnf> will do.
514 =head2 Timestamp Request
516 To create a timestamp request for F<design1.txt> with SHA-256 digest,
517 without nonce and policy, and without requirement for a certificate
520 openssl ts -query -data design1.txt -no_nonce \
523 To create a similar timestamp request with specifying the message imprint
526 openssl ts -query -digest b7e5d3f93198b38379852f2c04e78d73abdd0f4b \
527 -no_nonce -out design1.tsq
529 To print the content of the previous request in human readable format:
531 openssl ts -query -in design1.tsq -text
533 To create a timestamp request which includes the SHA-512 digest
534 of F<design2.txt>, requests the signer certificate and nonce, and
535 specifies a policy id (assuming the tsa_policy1 name is defined in the
536 OID section of the config file):
538 openssl ts -query -data design2.txt -sha512 \
539 -tspolicy tsa_policy1 -cert -out design2.tsq
541 =head2 Timestamp Response
543 Before generating a response a signing certificate must be created for
544 the TSA that contains the B<timeStamping> critical extended key usage extension
545 without any other key usage extensions. You can add this line to the
546 user certificate section of the config file to generate a proper certificate;
548 extendedKeyUsage = critical,timeStamping
550 See L<openssl-req(1)>, L<openssl-ca(1)>, and L<openssl-x509(1)> for
551 instructions. The examples below assume that F<cacert.pem> contains the
552 certificate of the CA, F<tsacert.pem> is the signing certificate issued
553 by F<cacert.pem> and F<tsakey.pem> is the private key of the TSA.
555 To create a timestamp response for a request:
557 openssl ts -reply -queryfile design1.tsq -inkey tsakey.pem \
558 -signer tsacert.pem -out design1.tsr
560 If you want to use the settings in the config file you could just write:
562 openssl ts -reply -queryfile design1.tsq -out design1.tsr
564 To print a timestamp reply to stdout in human readable format:
566 openssl ts -reply -in design1.tsr -text
568 To create a timestamp token instead of timestamp response:
570 openssl ts -reply -queryfile design1.tsq -out design1_token.der -token_out
572 To print a timestamp token to stdout in human readable format:
574 openssl ts -reply -in design1_token.der -token_in -text -token_out
576 To extract the timestamp token from a response:
578 openssl ts -reply -in design1.tsr -out design1_token.der -token_out
580 To add 'granted' status info to a timestamp token thereby creating a
583 openssl ts -reply -in design1_token.der -token_in -out design1.tsr
585 =head2 Timestamp Verification
587 To verify a timestamp reply against a request:
589 openssl ts -verify -queryfile design1.tsq -in design1.tsr \
590 -CAfile cacert.pem -untrusted tsacert.pem
592 To verify a timestamp reply that includes the certificate chain:
594 openssl ts -verify -queryfile design2.tsq -in design2.tsr \
597 To verify a timestamp token against the original data file:
598 openssl ts -verify -data design2.txt -in design2.tsr \
601 To verify a timestamp token against a message imprint:
602 openssl ts -verify -digest b7e5d3f93198b38379852f2c04e78d73abdd0f4b \
603 -in design2.tsr -CAfile cacert.pem
605 You could also look at the 'test' directory for more examples.
609 =for openssl foreign manuals: procmail(1), perl(1)
615 No support for timestamps over SMTP, though it is quite easy
616 to implement an automatic e-mail based TSA with L<procmail(1)>
617 and L<perl(1)>. HTTP server support is provided in the form of
618 a separate apache module. HTTP client support is provided by
619 L<tsget(1)>. Pure TCP/IP protocol is not supported.
623 The file containing the last serial number of the TSA is not
624 locked when being read or written. This is a problem if more than one
625 instance of L<openssl(1)> is trying to create a timestamp
626 response at the same time. This is not an issue when using the apache
627 server module, it does proper locking.
631 Look for the FIXME word in the source files.
635 The source code should really be reviewed by somebody else, too.
639 More testing is needed, I have done only some basic tests (see
651 L<openssl-genrsa(1)>,
656 Copyright 2006-2019 The OpenSSL Project Authors. All Rights Reserved.
658 Licensed under the Apache License 2.0 (the "License"). You may not use
659 this file except in compliance with the License. You can obtain a copy
660 in the file LICENSE in the source distribution or at
661 L<https://www.openssl.org/source/license.html>.