aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-07-17 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-07-17 00:00:00 +0000
commit9acac87485de47a1d8de704e6f49ecb79da5cff92b80dc5797d5bdd0ac452059 (patch)
treed71e06503e2fe9d7e206a409023b696d8a6e36c4f9e027d19bff4ba8ca6a66d0
parentde5d7ca0aee2fae473e79acbc34a47b433a7180f87dc4c53cb9cd4d77c73a62e (diff)
Clarify language
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 882ee1f..a49ac3c 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ Annotated [Git tag objects](https://git-scm.com/docs/user-manual.html#tag-object
There is another timestamp which comes from the optional GnuPG signature on a commit or annotated tag. It is controlled by GnuPG.
-### Removing Timestamps for Commits and Annotated Tags
+### Obfuscating Timestamps for Commits and Annotated Tags
Git can't remove timestamps altogether, but the `GIT_AUTHOR_DATE` and `GIT_COMMITTER_DATE` environment variables can be set to any arbitrary date. Preferably, use dates from before Git was invented to clearly signal the timestamps are forged:
@@ -41,7 +41,7 @@ export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"
Environment variables don't change after being set, so the dates update when a new shell is opened, not at midnight.
-### 🔑 Removing Timestamps for Digital Signatures 🔑
+### 🔑 Obfuscating Timestamps for Digital Signatures 🔑
GnuPG can't remove its signature timestamps altogether, but they can be forged by configuring Git to run a custom version of GnuPG: