Lines Matching +full:timestamp +full:- +full:names
18 .\" Set up some character translations and predefined strings. \*(-- will
24 .tr \(*W-
27 . ds -- \(*W-
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
37 . ds -- \|\(em\|
71 .\" Fear. Run. Save yourself. No user-serviceable parts.
81 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
97 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
98 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
99 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
100 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
101 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
102 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
104 . \" troff and (daisy-wheel) nroff accents
123 . ds d- d\h'-1'\(ga
124 . ds D- D\h'-1'\(hy
134 .TH TSGET 1ossl "2023-09-19" "3.0.11" "OpenSSL"
140 tsget \- Time Stamping HTTP/HTTPS client
144 \&\fB\-h\fR \fIserver_url\fR
145 [\fB\-e\fR \fIextension\fR]
146 [\fB\-o\fR \fIoutput\fR]
147 [\fB\-v\fR]
148 [\fB\-d\fR]
149 [\fB\-k\fR \fIprivate_key.pem\fR]
150 [\fB\-p\fR \fIkey_password\fR]
151 [\fB\-c\fR \fIclient_cert.pem\fR]
152 [\fB\-C\fR \fICA_certs.pem\fR]
153 [\fB\-P\fR \fICA_path\fR]
154 [\fB\-r\fR \fIfiles\fR]
155 [\fB\-g\fR \fIEGD_socket\fR]
159 This command can be used for sending a timestamp request, as specified
160 in \s-1RFC 3161,\s0 to a timestamp server over \s-1HTTP\s0 or \s-1HTTPS\s0 and storing the
161 timestamp response in a file. It cannot be used for creating the requests
162 and verifying responses, you have to use \fBopenssl\-ts\fR\|(1) to do that. This
163 command can send several requests to the server without closing the \s-1TCP\s0
166 This command sends the following \s-1HTTP\s0 request for each timestamp request:
170 \& User\-Agent: OpenTSA tsget.pl/<version>
172 \& Pragma: no\-cache
173 \& Content\-Type: application/timestamp\-query
174 \& Accept: application/timestamp\-reply
175 \& Content\-Length: length of body
180 It expects a response of type application/timestamp\-reply, which is
184 .IP "\fB\-h\fR \fIserver_url\fR" 4
185 .IX Item "-h server_url"
186 The \s-1URL\s0 of the \s-1HTTP/HTTPS\s0 server listening for timestamp requests.
187 .IP "\fB\-e\fR \fIextension\fR" 4
188 .IX Item "-e extension"
189 If the \fB\-o\fR option is not given this argument specifies the extension of the
192 .IP "\fB\-o\fR \fIoutput\fR" 4
193 .IX Item "-o output"
195 server. The timestamp response will be written to the given output file. '\-'
196 means standard output. In case of multiple timestamp requests or the absence
197 of this argument the names of the output files will be derived from the names
199 .IP "\fB\-v\fR" 4
200 .IX Item "-v"
203 .IP "\fB\-d\fR" 4
204 .IX Item "-d"
207 .IP "\fB\-k\fR \fIprivate_key.pem\fR" 4
208 .IX Item "-k private_key.pem"
209 (\s-1HTTPS\s0) In case of certificate-based client authentication over \s-1HTTPS\s0
211 file can optionally be protected by a passphrase. The \fB\-c\fR option must also
213 .IP "\fB\-p\fR \fIkey_password\fR" 4
214 .IX Item "-p key_password"
215 (\s-1HTTPS\s0) Specifies the passphrase for the private key specified by the \fB\-k\fR
218 .IP "\fB\-c\fR \fIclient_cert.pem\fR" 4
219 .IX Item "-c client_cert.pem"
220 (\s-1HTTPS\s0) In case of certificate-based client authentication over \s-1HTTPS\s0
221 \&\fIclient_cert.pem\fR must contain the X.509 certificate of the user. The \fB\-k\fR
223 certificate-based client authentication will take place. (Optional)
224 .IP "\fB\-C\fR \fICA_certs.pem\fR" 4
225 .IX Item "-C CA_certs.pem"
226 (\s-1HTTPS\s0) The trusted \s-1CA\s0 certificate store. The certificate chain of the peer's
227 certificate must include one of the \s-1CA\s0 certificates specified in this file.
228 Either option \fB\-C\fR or option \fB\-P\fR must be given in case of \s-1HTTPS.\s0 (Optional)
229 .IP "\fB\-P\fR \fICA_path\fR" 4
230 .IX Item "-P CA_path"
231 (\s-1HTTPS\s0) The path containing the trusted \s-1CA\s0 certificates to verify the peer's
232 certificate. The directory must be prepared with \fBopenssl\-rehash\fR\|(1). Either
233 option \fB\-C\fR or option \fB\-P\fR must be given in case of \s-1HTTPS.\s0 (Optional)
234 .IP "\fB\-r\fR \fIfiles\fR" 4
235 .IX Item "-r files"
237 .IP "\fB\-g\fR \fIEGD_socket\fR" 4
238 .IX Item "-g EGD_socket"
239 The name of an \s-1EGD\s0 socket to get random data from. (Optional)
242 List of files containing \s-1RFC 3161\s0 DER-encoded timestamp requests. If no
248 The \fB\s-1TSGET\s0\fR environment variable can optionally contain default
254 timestamp requests, tsa.opentsa.org listens at port 8080 for \s-1HTTP\s0 requests
255 and at port 8443 for \s-1HTTPS\s0 requests, the \s-1TSA\s0 service is available at the /tsa
258 Get a timestamp response for \fIfile1.tsq\fR over \s-1HTTP,\s0 output is written to
262 \& tsget \-h http://tsa.opentsa.org:8080/tsa file1.tsq
265 Get a timestamp response for \fIfile1.tsq\fR and \fIfile2.tsq\fR over \s-1HTTP\s0 showing
269 \& tsget \-h http://tsa.opentsa.org:8080/tsa \-v \-e .reply \e
273 Create a timestamp request, write it to \fIfile3.tsq\fR, send it to the server and
277 \& openssl ts \-query \-data file3.txt \-cert | tee file3.tsq \e
278 \& | tsget \-h http://tsa.opentsa.org:8080/tsa \e
279 \& \-o file3.tsr
282 Get a timestamp response for \fIfile1.tsq\fR over \s-1HTTPS\s0 without client
286 \& tsget \-h https://tsa.opentsa.org:8443/tsa \e
287 \& \-C cacerts.pem file1.tsq
290 Get a timestamp response for \fIfile1.tsq\fR over \s-1HTTPS\s0 with certificate-based
295 \& tsget \-h https://tsa.opentsa.org:8443/tsa \-C cacerts.pem \e
296 \& \-k client_key.pem \-c client_cert.pem file1.tsq
299 You can shorten the previous command line if you make use of the \fB\s-1TSGET\s0\fR
304 \& TSGET=\*(Aq\-h https://tsa.opentsa.org:8443/tsa \-C cacerts.pem \e
305 \& \-k client_key.pem \-c client_cert.pem\*(Aq
312 \&\fBopenssl\-ts\fR\|(1),
314 <https://www.rfc\-editor.org/rfc/rfc3161.html>
317 Copyright 2006\-2020 The OpenSSL Project Authors. All Rights Reserved.
321 in the file \s-1LICENSE\s0 in the source distribution or at