From f4bdf43856348bc92f1376f75a9f215491490785 Mon Sep 17 00:00:00 2001 From: kakwa Date: Wed, 2 Nov 2016 19:23:46 +0100 Subject: [PATCH] typo in README.rst --- README.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 9a42ee4..0881248 100644 --- a/README.rst +++ b/README.rst @@ -36,7 +36,7 @@ An RFC 3161 time-stamp is basically a cryptographic signature with a date attach 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. -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. 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).