security-and-privacy/uts-server
security-and-privacy/uts-server
1
0
Fork 0
mirror of https://github.com/kakwa/uts-server synced 2024-11-05 09:18:50 +01:00
Code Issues Releases Wiki Activity
199 Commits 2 Branches 15 Tags 500 KiB
C 76.4%
Shell 12.4%
CMake 6.5%
HTML 3.7%
Python 1%
c697886620
Go to file
kakwa c697886620 fixing missing dependency on compilation order 
add a dependency to compile civetweb before uts-server if civetweb
is bundled with uts-server.
2016-12-04 15:08:46 +01:00
cmake use civetweb 2016-08-19 00:04:13 +02:00
conf more secure cryptographic algorithm in example configuration 2016-09-12 22:43:00 +02:00
docs make the generation of the parameters completely automatic 2016-09-23 22:35:34 +02:00
goodies make the generation of the parameters completely automatic 2016-09-23 22:35:34 +02:00
inc format code 2016-12-04 13:39:27 +01:00
src format code 2016-12-04 13:39:27 +01:00
tests more secure cryptographic algorithm in example configuration 2016-09-12 22:43:00 +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 cleaning the travis.yml file 2016-12-04 14:10:30 +01:00
ChangeLog.rst changelog 2016-12-04 14:34:32 +01:00
CMakeLists.txt fixing missing dependency on compilation order 2016-12-04 15:08:46 +01:00
LICENSE Initial commit 2015-12-16 22:13:06 +01:00
README.rst fix typo 2 2016-11-02 19:25:01 +01:00

README.rst

uts-server

image

image

Documentation Status

Micro RFC 3161 Time-Stamp server written in C.

Doc

Uts-Server documentation on ReadTheDoc

Dev

Uts-Server source code on GitHub

License

MIT

Author

Pierre-Francois Carpentier - copyright © 2016

License

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, like 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 Start

# Building with civetweb embedded (will recover civetweb from github).
$ cmake . -DBUNDLE_CIVETWEB=ON
$ 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

image

image