fetch_git_signing_keys.sh: an attempt to store known signing keys and show which ones are not publicly available (unfound_keys_users.txt) #1804
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An attempt (PoC) to keep past git commit signing keys under Heads repo, since #1794 was opened.
See https://github.com/linuxboot/heads/blob/de5cc493662ed55b61c2e4de231589ca090528ff/git_signing_keys/README.md for Doc.
Note that each git commit signs the whole tree (think about blockchain if you will as @JonathonHall-Purism specified under comment #1794 (comment)
This experiment shows that some public keys were revoked/not on public servers. Doing multiple runs, selecting different different key servers (randomly) to fetch different keys confirms on console that no keys are changed even if fetched from different servers. Imperfect, but better then nothing.
I do not intend to merge this PR, but some keys are missing and I agree, users trying to use
git log --show-signature
will show commits that cannot be validated even if they were signed with a valid public key in the past. This PR shows that some keys, still valid today, cannot be found publicly easily, and some used in the past are nowhere to be found anymore. The point is still that those were valid at time of merge and should one way or the other be part of something, somewhere, at least from now on? @JonathonHall-Purism thoughts?This is output of file unfound_keys_users.txt from this experiment:
Also linked to 3mdeb/3mdeb-secpack#75 for 3mdeb keys not being on public gpg key servers today. For other keys, not sure what to do but have this, written somewhere to state that: those contributors contributions were reviewed prior of merging, while @osresearch (Trammel Hudson) merged his own commits at the early stages of this project, when this repo was under https://github.com/osresearch/heads, and those bases were read, and read and read again, on which this project evolved. More discussions under #1794 (which will not happen in the short term, and reasons why there as well).