2006-02-13 07:11:56 +08:00
|
|
|
=pod
|
|
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
|
|
|
|
|
tsget - Time Stamping HTTP/HTTPS client
|
|
|
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
|
|
|
|
|
B<tsget>
|
2019-10-02 03:26:16 +08:00
|
|
|
B<-h> I<server_url>
|
|
|
|
|
[B<-e> I<extension>]
|
|
|
|
|
[B<-o> I<output>]
|
2006-02-13 07:11:56 +08:00
|
|
|
[B<-v>]
|
|
|
|
|
[B<-d>]
|
2019-10-02 03:26:16 +08:00
|
|
|
[B<-k> I<private_key.pem>]
|
|
|
|
|
[B<-p> I<key_password>]
|
|
|
|
|
[B<-c> I<client_cert.pem>]
|
|
|
|
|
[B<-C> I<CA_certs.pem>]
|
|
|
|
|
[B<-P> I<CA_path>]
|
|
|
|
|
[B<-r> I<files>]
|
|
|
|
|
[B<-g> I<EGD_socket>]
|
|
|
|
|
[I<request> ...]
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
This command can be used for sending a timestamp request, as specified
|
2019-10-05 05:09:19 +08:00
|
|
|
in RFC 3161, to a timestamp server over HTTP or HTTPS and storing the
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
timestamp response in a file. It cannot be used for creating the requests
|
|
|
|
|
and verifying responses, you have to use L<openssl-ts(1)> to do that. This
|
|
|
|
|
command can send several requests to the server without closing the TCP
|
|
|
|
|
connection if more than one requests are specified on the command line.
|
2006-02-13 07:11:56 +08:00
|
|
|
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
This command sends the following HTTP request for each timestamp request:
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2016-05-20 20:11:46 +08:00
|
|
|
POST url HTTP/1.1
|
|
|
|
|
User-Agent: OpenTSA tsget.pl/<version>
|
|
|
|
|
Host: <host>:<port>
|
|
|
|
|
Pragma: no-cache
|
|
|
|
|
Content-Type: application/timestamp-query
|
|
|
|
|
Accept: application/timestamp-reply
|
|
|
|
|
Content-Length: length of body
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2016-05-20 20:11:46 +08:00
|
|
|
...binary request specified by the user...
|
2006-02-13 07:11:56 +08:00
|
|
|
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
It expects a response of type application/timestamp-reply, which is
|
2006-02-13 07:11:56 +08:00
|
|
|
written to a file without any interpretation.
|
|
|
|
|
|
|
|
|
|
=head1 OPTIONS
|
|
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-h> I<server_url>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-09-28 01:17:09 +08:00
|
|
|
The URL of the HTTP/HTTPS server listening for timestamp requests.
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-e> I<extension>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
If the B<-o> option is not given this argument specifies the extension of the
|
|
|
|
|
output files. The base name of the output file will be the same as those of
|
2019-10-02 03:26:16 +08:00
|
|
|
the input files. Default extension is F<.tsr>. (Optional)
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-o> I<output>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
This option can be specified only when just one request is sent to the
|
2019-09-28 01:17:09 +08:00
|
|
|
server. The timestamp response will be written to the given output file. '-'
|
|
|
|
|
means standard output. In case of multiple timestamp requests or the absence
|
2006-02-13 07:11:56 +08:00
|
|
|
of this argument the names of the output files will be derived from the names
|
|
|
|
|
of the input files and the default or specified extension argument. (Optional)
|
|
|
|
|
|
|
|
|
|
=item B<-v>
|
|
|
|
|
|
|
|
|
|
The name of the currently processed request is printed on standard
|
|
|
|
|
error. (Optional)
|
|
|
|
|
|
|
|
|
|
=item B<-d>
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=for comment perlpodstyle(1) says to refer to modules without section
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
Switches on verbose mode for the underlying perl module L<WWW::Curl::Easy>.
|
|
|
|
|
You can see detailed debug messages for the connection. (Optional)
|
|
|
|
|
|
|
|
|
|
=item B<-k> I<private_key.pem>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
(HTTPS) In case of certificate-based client authentication over HTTPS
|
2019-10-02 03:26:16 +08:00
|
|
|
I<private_key.pem> must contain the private key of the user. The private key
|
2006-02-13 07:11:56 +08:00
|
|
|
file can optionally be protected by a passphrase. The B<-c> option must also
|
|
|
|
|
be specified. (Optional)
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-p> I<key_password>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
(HTTPS) Specifies the passphrase for the private key specified by the B<-k>
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
argument. If this option is omitted and the key is passphrase protected,
|
|
|
|
|
it will be prompted for. (Optional)
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-c> I<client_cert.pem>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
(HTTPS) In case of certificate-based client authentication over HTTPS
|
2019-10-02 03:26:16 +08:00
|
|
|
I<client_cert.pem> must contain the X.509 certificate of the user. The B<-k>
|
2006-02-13 07:11:56 +08:00
|
|
|
option must also be specified. If this option is not specified no
|
|
|
|
|
certificate-based client authentication will take place. (Optional)
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-C> I<CA_certs.pem>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
(HTTPS) The trusted CA certificate store. The certificate chain of the peer's
|
|
|
|
|
certificate must include one of the CA certificates specified in this file.
|
|
|
|
|
Either option B<-C> or option B<-P> must be given in case of HTTPS. (Optional)
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-P> I<CA_path>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
(HTTPS) The path containing the trusted CA certificates to verify the peer's
|
Command docs: fix up command references
Almost all OpenSSL commands are in reality 'openssl cmd', so make sure
they are refered to like that and not just as the sub-command.
Self-references are avoided as much as is possible, and replaced with
"this command". In some cases, we even avoid that with a slight
rewrite of the sentence or paragrah they were in. However, in the few
cases where a self-reference is still admissible, they are done in
bold, i.e. openssl-speed.pod references itself like this:
B<openssl speed>
References to other commands are done as manual links, i.e. CA.pl.pod
references 'openssl req' like this: L<openssl-req(1)>
Some commands are examples rather than references; we enclose those in
C<>.
While we are it, we abolish "utility", replacing it with "command", or
remove it entirely in some cases.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/10065)
2019-10-02 01:43:36 +08:00
|
|
|
certificate. The directory must be prepared with L<openssl-rehash(1)>. Either
|
|
|
|
|
option B<-C> or option B<-P> must be given in case of HTTPS. (Optional)
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-r> I<files>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-04 10:28:40 +08:00
|
|
|
See L<openssl(1)/Random State Options> for more information.
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item B<-g> I<EGD_socket>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
The name of an EGD socket to get random data from. (Optional)
|
|
|
|
|
|
2019-10-02 03:26:16 +08:00
|
|
|
=item I<request> ...
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-05 05:09:19 +08:00
|
|
|
List of files containing RFC 3161 DER-encoded timestamp requests. If no
|
2019-10-02 03:26:16 +08:00
|
|
|
requests are specified only one request will be sent to the server and it will
|
|
|
|
|
be read from the standard input.
|
|
|
|
|
(Optional)
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
=back
|
|
|
|
|
|
|
|
|
|
=head1 ENVIRONMENT VARIABLES
|
|
|
|
|
|
|
|
|
|
The B<TSGET> environment variable can optionally contain default
|
|
|
|
|
arguments. The content of this variable is added to the list of command line
|
|
|
|
|
arguments.
|
|
|
|
|
|
|
|
|
|
=head1 EXAMPLES
|
|
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
The examples below presume that F<file1.tsq> and F<file2.tsq> contain valid
|
2019-09-28 01:17:09 +08:00
|
|
|
timestamp requests, tsa.opentsa.org listens at port 8080 for HTTP requests
|
2006-02-13 07:11:56 +08:00
|
|
|
and at port 8443 for HTTPS requests, the TSA service is available at the /tsa
|
|
|
|
|
absolute path.
|
|
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
Get a timestamp response for F<file1.tsq> over HTTP, output is written to
|
|
|
|
|
F<file1.tsr>:
|
2010-01-06 01:16:54 +08:00
|
|
|
|
2006-02-13 07:11:56 +08:00
|
|
|
tsget -h http://tsa.opentsa.org:8080/tsa file1.tsq
|
|
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
Get a timestamp response for F<file1.tsq> and F<file2.tsq> over HTTP showing
|
|
|
|
|
progress, output is written to F<file1.reply> and F<file2.reply> respectively:
|
2010-01-06 01:16:54 +08:00
|
|
|
|
2006-02-13 07:11:56 +08:00
|
|
|
tsget -h http://tsa.opentsa.org:8080/tsa -v -e .reply \
|
2016-05-20 20:11:46 +08:00
|
|
|
file1.tsq file2.tsq
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
Create a timestamp request, write it to F<file3.tsq>, send it to the server and
|
|
|
|
|
write the response to F<file3.tsr>:
|
2010-01-06 01:16:54 +08:00
|
|
|
|
2006-02-13 07:11:56 +08:00
|
|
|
openssl ts -query -data file3.txt -cert | tee file3.tsq \
|
2016-05-20 20:11:46 +08:00
|
|
|
| tsget -h http://tsa.opentsa.org:8080/tsa \
|
|
|
|
|
-o file3.tsr
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
Get a timestamp response for F<file1.tsq> over HTTPS without client
|
2006-02-13 07:11:56 +08:00
|
|
|
authentication:
|
2010-01-06 01:16:54 +08:00
|
|
|
|
2006-02-13 07:11:56 +08:00
|
|
|
tsget -h https://tsa.opentsa.org:8443/tsa \
|
2016-05-20 20:11:46 +08:00
|
|
|
-C cacerts.pem file1.tsq
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2019-10-02 02:19:45 +08:00
|
|
|
Get a timestamp response for F<file1.tsq> over HTTPS with certificate-based
|
|
|
|
|
client authentication (it will ask for the passphrase if F<client_key.pem> is
|
2006-02-13 07:11:56 +08:00
|
|
|
protected):
|
|
|
|
|
|
|
|
|
|
tsget -h https://tsa.opentsa.org:8443/tsa -C cacerts.pem \
|
2016-05-20 20:11:46 +08:00
|
|
|
-k client_key.pem -c client_cert.pem file1.tsq
|
2006-02-13 07:11:56 +08:00
|
|
|
|
|
|
|
|
You can shorten the previous command line if you make use of the B<TSGET>
|
|
|
|
|
environment variable. The following commands do the same as the previous
|
|
|
|
|
example:
|
|
|
|
|
|
|
|
|
|
TSGET='-h https://tsa.opentsa.org:8443/tsa -C cacerts.pem \
|
2016-05-20 20:11:46 +08:00
|
|
|
-k client_key.pem -c client_cert.pem'
|
2006-02-13 07:11:56 +08:00
|
|
|
export TSGET
|
|
|
|
|
tsget file1.tsq
|
|
|
|
|
|
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
|
2019-10-25 04:40:11 +08:00
|
|
|
=for openssl foreign manual WWW::Curl::Easy
|
2016-11-11 16:33:47 +08:00
|
|
|
|
2019-08-22 07:04:41 +08:00
|
|
|
L<openssl(1)>,
|
|
|
|
|
L<openssl-ts(1)>,
|
2019-10-02 03:26:16 +08:00
|
|
|
L<WWW::Curl::Easy>,
|
2019-10-05 05:09:19 +08:00
|
|
|
L<https://www.rfc-editor.org/rfc/rfc3161.html>
|
2006-02-13 07:11:56 +08:00
|
|
|
|
2016-05-18 23:44:05 +08:00
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
2019-08-22 07:04:41 +08:00
|
|
|
Copyright 2006-2019 The OpenSSL Project Authors. All Rights Reserved.
|
2016-05-18 23:44:05 +08:00
|
|
|
|
2018-12-06 21:04:11 +08:00
|
|
|
Licensed under the Apache License 2.0 (the "License"). You may not use
|
2016-05-18 23:44:05 +08:00
|
|
|
this file except in compliance with the License. You can obtain a copy
|
|
|
|
|
in the file LICENSE in the source distribution or at
|
|
|
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
|
|
|
|
|
|
=cut
|
