Publication of timestamps issued by gitta.zeitgitter.net
Find a file
2026-01-09 15:23:37 +00:00
hashes.asc Newly timestamped commits up to 2025-12-19 13:05:28 UTC 2025-12-19 13:23:37 +00:00
hashes.log Newly timestamped commits up to 2026-01-09 15:23:04 UTC 2026-01-09 15:23:37 +00:00
pubkey.asc Renamed to gitta.zeitgitter.net 2019-05-12 20:39:54 +02:00
README.md Outage with data loss. Sorry! 2020-08-13 17:44:40 +02:00

Timestamping log for gitta.zeitgitter.net

This lists all commit IDs for which gitta.zeitgitter.net (previously known as gitta.enotar.ch) has ever issued a timestamp signature. If there are any other signatures, please do consider them invalid.

This is part of the Zeitgitter distributed timestamping system. Please learn more about Zeitgitter at https://zeitgitter.net .

Verify timestamping log

To verify whether a given commit is in there, e.g., one dated at 2019-04-01 19:30, please use the following commands on a checked-out copy of this repository:

git checkout `git rev-list --since="2019-04-01 19:30" --reverse master | head -1`

You should be able to find the commit ID in hashes.log then.

Outage with data loss

  • 2020-08-13 from 09:23:37 to 15:23:37 UTC: A misconfiguration (lack of git in the Docker image) triggered a software bug (important exceptions were ignored), leading to irrecoverable data loss. We are extremely sorry this happened. If, in the future, there should ever be any doubt about abuse of this server's private key, please consider any signatures in this time frame as suspect, as they are not recorded and thus not properly cross-timestamped. Thus rely on the secrecy of this server's secret key only. As far as I (Marcel Waldvogel) can tell, only timestamps issued under my control were lost. If other people have been impacted, they should obtain a new timestamp, reverting to diversity.zeitgitter.net, if git timestamp claims a timestamp has already been issued for the current commit.