13 Commits

Author	SHA1	Message	Date
Phil Davis	d48097695b	feature: validate commits in reverse date-time order when MAX_COMMITS_TO_CHECK is used ... This ensures that the most recent commits are the ones that are validated.	2025-06-03 17:21:42 +05:45
Phil Davis	f712aa0822	chore: adjust comment about MAX_COMMITS_TO_CHECK	2025-06-02 15:32:48 +05:45
Phil Davis	8aba6e98d1	fix: stop correctly when MAX_COMMITS_TO_CHECK is reached	2025-06-02 14:32:23 +05:45
Phil Davis	4437b66f67	feature: default to checking all commits	2025-05-29 09:55:57 +05:45
Phil Davis	aabd314dde	feature: limit the number of commits to be validated ... Signed-off-by: Phil Davis <phil@jankaritech.com>	2025-05-28 10:56:06 +05:45
Phil Davis	2976a241af	only validate each commit once	2025-03-18 13:47:27 +05:45
Artur Neumann	f397c5f7fd	set execute permission on hooks ... that way one does not need to remember to set the permissions after copieng the hooks	2025-01-24 13:34:46 +05:45
Artur Neumann	3a2668f7ad	Merge pull request 'fix comparison' (#2) from fixComparison into main ... Reviewed-on: #2 Reviewed-by: phil <phil@jankaritech.eu>	2025-01-24 06:55:07 +00:00
Artur Neumann	d134bc0c11	fix comparison ... spaces are needed around the comparison operator. See https://github.com/koalaman/shellcheck/wiki/SC2077 This fixes the issue that even `validate.sh` finds an issue the return code is `0`	2025-01-10 16:24:48 +05:45
Artur Neumann	0e523bd1ee	fix running validate with -v ... running ./.git/hooks/validate.sh -v gives me Assertion failed: Precondition: hash -v must have length 64. Backtrace: [1]: ./.git/hooks/timestamping : extract_token_from_commit line 200 [2]: ./.git/hooks/validate.sh : validate_commit line 97 [3]: ./.git/hooks/validate.sh : validate_commit_and_parents line 300 [4]: ./.git/hooks/validate.sh : main line 329 this commit fixes the issue	2025-01-10 15:52:58 +05:45
Matthias Bühlmann	83c16a2f77	Changed validate.sh to only trust latest timestamp commit version ... added arguments to validate.sh --verbose to generate verbose output --minversion to specify minimum timestamp commit version to be trust	2021-02-21 19:19:27 +01:00
Matthias Bühlmann	80034aeb78	Changed digest that is being timestamped ... Changed digest that is being stamped from $parent_commit_hash, to shaX(parent:$parent_commit_hash,tree:$tree_hash) where shaX is the hash function used by the repository. This change is so that the timestamp added also timestamps the LTV data that is being added with the timestamp commit. This LTV data now also contains CRLs for the LAST timestamp commit. This ensures that timestamp lifetime of old timestamps gets arbitrarily extended into the future with every new timestamp added to the repository. Further changes: -Updated documentation -updated schematics and changed from SVG to PNG -added assertions, pre- and post-conditions -added version number to timestamp commits as trailer -added hashing algorithm used as trailer -added digest being timestamped as trailer -added the string that is hashed to get the digest as traile -improved log messages of validate.sh	2021-02-21 18:19:05 +01:00
Matthias Bühlmann	d6ef1a5b02	Added verification script to verify all timestamps in the repository. ... Updated Documentation.	2021-02-16 10:05:26 +01:00