Lines Matching refs:token
78 signs them and sends the timestamp token back to the client. By
79 creating this token the TSA certifies the existence of the original
84 The TSA client receives the timestamp token and verifies the
85 signature on it. It also checks if the token contains the same hash
159 timestamp token. Either the dotted OID notation or OID names defined
199 and the timestamp token itself (ContentInfo), if the token generation was
201 response or timestamp token based on a request and printing the
202 response/token in human-readable format. If B<-token_out> is not
204 otherwise it is a timestamp token (ContentInfo).
266 Specifies a previously created timestamp response or timestamp token
270 token or you want to extract the timestamp token from a response. If
271 the input is a token and the output is a timestamp response a default
272 'granted' status info is added to the token. (Optional)
277 that the input is a DER encoded timestamp token (ContentInfo) instead
288 The output is a timestamp token (ContentInfo) instead of timestamp
305 timestamp token is valid and matches a particular timestamp request or
312 The response or token must be verified against file_to_hash. The file
313 is hashed with the message digest algorithm specified in the token.
319 The response or token must be verified against the message digest specified
321 specified in the token. The B<-data> and B<-queryfile> options must not be
336 that the input is a DER encoded timestamp token (ContentInfo) instead
557 To create a timestamp token instead of timestamp response:
561 To print a timestamp token to stdout in human readable format:
565 To extract the timestamp token from a response:
569 To add 'granted' status info to a timestamp token thereby creating a
586 To verify a timestamp token against the original data file:
591 To verify a timestamp token against a message imprint:
