Timestamping client for zeitgitter
Project description
git timestamp
— Git Timestamper for Zeitgitter
Timestamping: Why?
Being able to provide evidence that you had some piece of information at a given time and it has not changed since are important in many aspects of personal, academic, or corporate life.
It can help provide evidence
- that you had some idea already at a given time,
- that you already had a piece of code, or
- that you knew about a document at a given time.
Timestamping does not assure authorship of the idea, code, or document. It only provides evidence to the existence at a given point in time. Depending on the context, authorship might be implied, at least weakly.
Zeitgitter for Timestamping
Zeitgitter consists of two components:
- A timestamping client,
git timestamp
, which can add a timestamp as a digital signature to an existinggit
repository. Existinggit
mechanisms can then be used to distribute these timestamps (stored in commits or tags) or keep them private. - A timestamping server,
zeitgitterd
, which supports timestampinggit
repositories and stores its history of commits timestamped in agit
repository as well. Anybody can operate such a timestamping server, but using an independent timestamper provides strongest evidence, as collusion is less likely.- Publication of the timestamps history; as well as
- getting cross-timestamps of other independent timestampers on your timestamp history both provide mechanisms to assure that timestamping has not been done retroactively ("backstamping").
The timestamping client is called git timestamp
and allows to issue
timestamped, signed tags or commits.
To simplify deployment, we provide a free timestamping server at https://gitta.enotar.ch. It is able to provide several million timestamps per day. However, if you or your organization plan to issue more than a hundred timestamps per day, please consider installing and using your own timestamping server and have it being cross-timestamped with other servers.
Client Usage
Options
usage: timestamp.py [-h] [--version] [--tag TAG] [--branch BRANCH]
[--server SERVER] [--gnupg-home GNUPG_HOME]
[--enable ENABLE] [--require-enable]
[COMMIT]
Interface to Zeitgitter, the network of independent GIT timestampers.
positional arguments:
- COMMIT: Which commit to timestamp. Can be set by
git config timestamp.commit-branch
; fallback default: 'HEAD'
optional arguments:
- -h, --help: Show this help message and exit. When called as
git timestamp
(space, not dash), use-h
, as--help
is captured bygit
itself. - --version: Show program's version number and exit
- --tag TAG: Create a new timestamped tag named TAG
- --branch BRANCH: Create a timestamped commit in branch BRANCH, with
identical contents as the specified commit. Default
name derived from servername plus
-timestamps
. Can be set bygit config timestamp.branch
- --server SERVER: Zeitgitter server to obtain timestamp from. Can be set
by
git config timestamp.server
; fallback default:https://gitta.zeitgitter.net
- --gnupg-home GNUPG_HOME:
Where to store timestamper public keys. Can be set by
git config
timestamp.gnupg-home
- --enable ENABLE: Forcibly enable/disable timestamping operations;
mainly for use in
git config
. Can be set bygit config timestamp.enable
- --require-enable: Disable operation unless
git config timestamp.enable
has explicitely been set to true
--tag
takes precedence over --branch
. When in doubt, use --tag
for
single/rare timestamping, and --branch
for reqular timestamping.
Inclusion in other packages
Timestamping can be a useful add-on feature for many operations, including
verifying whether a repository has been tampered with. For example, we use it
extensively together with etckeeper
for tamper-evidence.
If you would like to include timestamping as an optional component in your software, you have to first decide whether timestamping should be on or off by default for your software:
- default-on: Just call
git timestamp
as normal. Users can disable timestamping on a per-repository basis by runninggit config timestamp.enable false
at any time. - default-off: Timestamp with the option
--require-enable
. Then, users have to first rungit config timestamp.enable true
in the repository. In any case, you should check whethergit timestamp
has been installed before calling it. In a shell, you could do this as follows:
if which git-timestamp > /dev/null; then
git timestamp OPTIONS
fi
General and Client Documentation
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for git_timestamp-0.9.7-py2.py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 077c80f5bd8477464e32921a70e9853fab7b59fe3f3b403749cba9c257592fd3 |
|
MD5 | d29a10afd5af57c4c94e2c5ab3e1c2ee |
|
BLAKE2b-256 | 9e45706173db5f29c2eec131d9e12d0243982cdcaae2c73cbb89a10224b946f7 |