Go to file
kakwa c7b3f47325 version bump 2021-04-07 15:27:32 +02:00
cmake remove cmake warning + better comment 2017-04-21 08:59:20 +02:00
conf better handling for logging to stdout 2019-04-10 22:47:38 +02:00
docs improve documentation 2019-04-12 15:12:59 +02:00
goodies dl for the signer cert + fix example + css tweaks 2019-04-12 14:26:21 +02:00
inc fixing compilation errors and warnings 2021-04-07 15:23:54 +02:00
src fixing compilation errors and warnings 2021-04-07 15:23:54 +02:00
tests sleep unit tests (hopefully 2019-04-11 01:02:46 +02:00
.gitignore adding the configure.rst file in gitignore 2016-09-23 22:39:26 +02:00
.gitmodules remove submodule for civetweb 2016-09-07 20:56:02 +02:00
.travis.yml Update .travis.yml 2017-05-19 21:34:58 +02:00
CMakeLists.txt version bump 2021-04-07 15:27:32 +02:00
ChangeLog.rst version bump 2021-04-07 15:27:32 +02:00
Jenkinsfile Updated Jenkinsfile 2017-04-27 22:51:44 +02:00
LICENSE Initial commit 2015-12-16 22:13:06 +01:00
README.rst Update README.rst 2019-04-12 15:51:57 +02:00
_config.yml Set theme jekyll-theme-hacker 2017-12-06 21:08:54 +01:00





Documentation Status

Jenkins Status

Micro RFC 3161 Time-Stamp server written in C.


Uts-Server documentation on ReadTheDoc


Uts-Server source code on GitHub




Pierre-Francois Carpentier - copyright © 2019


A demo is accessible here: https://uts-server.kakwalab.ovh/


Released under the MIT Public License

What is RFC 3161?

An RFC 3161 time-stamp is basically a cryptographic signature with a date attached.

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 of like a signature).
  3. The Time-Stamp authority server returns 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).

It gives a cryptographic proof of a piece of data content, for example a file, at a given time.

Some use cases:

  • time-stamp log files at rotation time.
  • time-stamp file at upload to prove it was delivered in due time or not.

Quick (and dirty) Testing

Here a few steps to quickly try out uts-server, for production setup, please compile civetweb externally and create proper CA and certificates:

# Building with civetweb embedded (will recover civetweb from github).
# Note: the BUNDLE_CIVETWEB option is only here for fast testing purpose
# The recommended way to deploy uts-server in production is to build civetweb
# separatly and to link against it.
$ make

# Create some test certificates.
$ ./tests/cfg/pki/create_tsa_certs

# Launching the time-stamp server with test configuration in debug mode.
$ ./uts-server -c tests/cfg/uts-server.cnf -D

# In another shell, launching a time-stamp script on the README.md file.
$ ./goodies/timestamp-file.sh -i README.rst -u http://localhost:2020 -r -O "-cert";

# Verify the time-stamp.
$ openssl ts -verify -in README.rst.tsr -data README.rst -CAfile ./tests/cfg/pki/tsaca.pem

# Display the time-stamp content.
$ openssl ts -reply -in README.rst.tsr -text

Powered by