From: Petter Reinholdtsen Date: Tue, 25 Mar 2014 11:50:50 +0000 (+0000) Subject: Protocol agnostic. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/4937d8f2eba53afa504a327c7637ac7020e2056d?ds=inline Protocol agnostic. --- diff --git a/blog/data/2014-03-25-trusted-timestamping.txt b/blog/data/2014-03-25-trusted-timestamping.txt index 01b6859797..51d86c9c48 100644 --- a/blog/data/2014-03-25-trusted-timestamping.txt +++ b/blog/data/2014-03-25-trusted-timestamping.txt @@ -25,11 +25,13 @@ few years ago as RFC 3161. The mechanism is simple. Create a hash of the file in question, send it to a trusted third party which add a time stamp to the hash and sign the result with its private key, and send back the -signed hash + timestamp. Anyone with the document and the signature -can then verify that the document matches the signature by creating -their own hash and checking the signature using the trusted third -party public key. There are several commercial services around -providing such timestamping. A quick search for +signed hash + timestamp. Both email, FTP and HTTP can be used to +request such signature, depending on what is provided by the service +used. Anyone with the document and the signature can then verify that +the document matches the signature by creating their own hash and +checking the signature using the trusted third party public key. +There are several commercial services around providing such +timestamping. A quick search for "rfc 3161 service" pointed me to at least DigiStamp,