security-and-privacy/uts-server
security-and-privacy/uts-server
1
0
Fork 0
mirror of https://github.com/kakwa/uts-server synced 2025-01-10 13:44:29 +01:00
Code Issues Releases Wiki Activity

typo in README.rst

Browse Source
This commit is contained in:
kakwa 2016-11-02 19:23:46 +01:00
parent f7d8e6b2fe
commit b8b71d3a2a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -36,7 +36,7 @@ An RFC 3161 time-stamp is basically a cryptographic signature with a date attach
Roughly, it works as follow: Roughly, it works as follow:
1. A client application sends an hash of the data it wants to time-stamp to a Time-Stamp authority server. 1. A client application sends an hash of the data it wants to time-stamp to a Time-Stamp authority server.
2. The Time-Stamp authority server retrieves the current date, concatenates it with the hash and uses its private key to create the time-stamp (kind a like a signature). 2. The Time-Stamp authority server retrieves the current date, concatenates it with the hash and uses its private key to create the time-stamp (kind of like a signature).
3. The Time-Stamp authority server return the generated time-stamp to the client application. 3. The Time-Stamp authority server return the generated time-stamp to the client application.
Then a client can verify the piece of data with the time-stamp using the Certificate Authority of the time-stamp key pair (X509 certificates). Then a client can verify the piece of data with the time-stamp using the Certificate Authority of the time-stamp key pair (X509 certificates).