diff options
| -rw-r--r-- | content/about.md | 2 | ||||
| -rw-r--r-- | content/entry/why-i-timestamped-my-journal.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/content/about.md b/content/about.md index f96dce9..59af9de 100644 --- a/content/about.md +++ b/content/about.md @@ -76,5 +76,5 @@ To provide some assurance that I don't use AI tools to write this journal, I tim ```sh git clone --recursive https://git.nicholasjohnson.ch/journal -ots verify -d "$(git -C journal show-ref --hash signify-signature-10)" journal/static/static/timestamp-2.ots +ots verify -d "$(git -C journal show-ref --hash archive/signify-signature-10)" journal/static/static/timestamp-2.ots ``` diff --git a/content/entry/why-i-timestamped-my-journal.md b/content/entry/why-i-timestamped-my-journal.md index de31e47..428807b 100644 --- a/content/entry/why-i-timestamped-my-journal.md +++ b/content/entry/why-i-timestamped-my-journal.md @@ -33,7 +33,7 @@ Commands: ```sh git clone --recursive https://git.nicholasjohnson.ch/journal -ots verify -d "$(git -C journal show-ref --hash signify-signature-10)" journal/static/static/timestamp-2.ots +ots verify -d "$(git -C journal show-ref --hash archive/signify-signature-10)" journal/static/static/timestamp-2.ots ``` @@ -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=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. +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. 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. |