diff options
| author | Nicholas Johnson <> | 2025-06-23 00:00:00 +0000 |
|---|---|---|
| committer | Nicholas Johnson <> | 2025-06-23 00:00:00 +0000 |
| commit | c22b19be5adfc78c50ad6df79197230220f18f828a29a9eb3dd6a479d78a0e20 (patch) | |
| tree | d6b99179515318d47e64c70cc57848039ab954f1dd978f111d5a434e9b5a4204 /content/entry | |
| parent | df05aea8321e4e5fa36a024e0b8b663595c2539b4f1d2ceb285a2672b5658775 (diff) | |
| download | journal-c22b19be5adfc78c50ad6df79197230220f18f828a29a9eb3dd6a479d78a0e20.tar.gz journal-c22b19be5adfc78c50ad6df79197230220f18f828a29a9eb3dd6a479d78a0e20.zip | |
Diffstat (limited to 'content/entry')
| -rw-r--r-- | content/entry/why-i-timestamped-my-journal.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/why-i-timestamped-my-journal.md b/content/entry/why-i-timestamped-my-journal.md index 428807b..9304fca 100644 --- a/content/entry/why-i-timestamped-my-journal.md +++ b/content/entry/why-i-timestamped-my-journal.md @@ -45,6 +45,6 @@ Timestamp chaining could perhaps provide stronger assurance of the legitimacy of But one good idea contained in that entry was to restamp this journal's Git repo to future-proof its timestamp. The old timestamp was performed on the old repo which used the broken SHA-1 hashing algorithm. Since then, I converted the repo to the new SHA-2 object format and SHA-2 support in Git has been stabilized. So everything I needed to create a new, stronger timestamp was present. Well, almost everything. -The only issue I ran into was that the OpenTimestamps software does not have sufficient [Git integration](https://github.com/opentimestamps/opentimestamps-client/blob/master/doc/git-integration.md "OpenTimestamps Git Integration") to embed timestamps within Git objects in SHA-2 repos like it can for SHA-1 repos. So I just timestamped [the most recent tag](https://git.nicholasjohnson.ch/journal/tag/?h=archive%2Fsignify-signature-10 "Most Recent Tag of Journal Repo") manually, creating a fully separate [.ots proof file](/static/timestamp-2.ots "Timestamp Proof File") which is verified without using OpenTimestamps' GnuPG wrapper. +The only issue I ran into was that the OpenTimestamps software does not have sufficient [Git integration](https://github.com/opentimestamps/opentimestamps-client/blob/master/doc/git-integration.md "OpenTimestamps Git Integration") to embed timestamps within Git objects in SHA-2 repos like it can for SHA-1 repos. So I just timestamped [the most recent tag](https://git.nicholasjohnson.ch/journal/tag/?h=archive/signify-signature-10 "Most Recent Tag of Journal Repo") manually, creating a fully separate [.ots proof file](/static/timestamp-2.ots "Timestamp Proof File") which is verified without using OpenTimestamps' GnuPG wrapper. Hopefully the new timestamp lasts. If not, both [Software Heritage](https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://git.nicholasjohnson.ch/journal "Journal Repo on Software Heritage") and [Archive.org](https://web.archive.org/web/*/https://nicholasjohnson.ch/ "Journal on Archive.org") have centralized timestamps of this journal as fallbacks. |