Specify how to sign/verify AirgapOS hashes #26

Open
opened 2024-12-19 21:11:38 +00:00 by scjudd · 0 comments
Member

In the "Setup Steps" for AirgapOS:

  1. Commit the hash of airgap to a git repo, ensuring the commit is signed

Some more instruction here would be good:

  • Where should one commit this?
  • How to perform a signed commit?
  • How to establish that a particular commit signature 'means' something (i.e., we have a trusted keyring set up)
  • Where later in the process is this commit signature verified?
In the ["Setup Steps" for AirgapOS](https://git.distrust.co/public/docs/src/commit/57faca72fdb54682ca119f41c3250eee8cf7c795/quorum-key-management/src/one-time-use-airgapos.md#setup-steps): > 7. Commit the hash of airgap to a git repo, ensuring the commit is signed Some more instruction here would be good: - Where should one commit this? - How to perform a signed commit? - How to establish that a particular commit signature 'means' something (i.e., we have a trusted keyring set up) - Where later in the process is this commit signature verified?
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/docs#26
No description provided.