diff --git a/quorum-key-management/src/component-documents/tamper-evidence-methods.md b/quorum-key-management/src/component-documents/tamper-evidence-methods.md index 8ff3457..db3e8b1 100644 --- a/quorum-key-management/src/component-documents/tamper-evidence-methods.md +++ b/quorum-key-management/src/component-documents/tamper-evidence-methods.md @@ -119,9 +119,10 @@ Sealing bags of standard size objects which need to be protected can fit in. The 3. Use vacuum sealer to remove air from the bag until the beads are no longer able to move -4. Use the [Tamper Proofing Station](tamper-evidence-methods#tamper-proofing-station) to take a photograph of both sides of the sealed object using both the digital and polaroid camera +4. Take photographs of both sides of the sealed object using both the digital and polaroid camera 5. Take the SD card to an online connected device and commit the photographs to a repository, ensuring the commit is signed + // ANCHOR_END: vsbwf-procedure-sealing #### Unsealing diff --git a/quorum-key-management/src/generated-documents/level-2/fixed-location/approver/approve-transaction.md b/quorum-key-management/src/generated-documents/level-2/fixed-location/approver/approve-transaction.md index 3b23da5..0925f12 100644 --- a/quorum-key-management/src/generated-documents/level-2/fixed-location/approver/approve-transaction.md +++ b/quorum-key-management/src/generated-documents/level-2/fixed-location/approver/approve-transaction.md @@ -8,7 +8,7 @@ The approver is responsible for verifying a transaction proposed by a [proposer] * Ensure that the computer is configured to sign commits with the desired key. Refer to the [Appendix: Git Commit Signing Configuration](#git-commit-signing-configuration) -* Clone the [Ceremonies Repository](/generated-documents/level-2/fixed-location/provisioner/ceremonies-repository.html) for your organization to the machine +* Clone the [Ceremonies Repository](../provisioner/provision-ceremonies-repository.md) for your organization to the machine ## Procedure @@ -29,7 +29,9 @@ The approver is responsible for verifying a transaction proposed by a [proposer] ## Appendix ### Git Commit Signing Configuration + {{ #include ../../../../component-documents/git-commit-signing.md:steps }} ### Generating PGP Keypair & Provisioning Smart Card + {{ #include ../../../../component-documents/openpgp-setup.md:steps-keyfork }} diff --git a/quorum-key-management/src/generated-documents/level-2/fixed-location/proposer/create-transaction-payload.md b/quorum-key-management/src/generated-documents/level-2/fixed-location/proposer/create-transaction-payload.md index fbf65fe..d8d7e47 100644 --- a/quorum-key-management/src/generated-documents/level-2/fixed-location/proposer/create-transaction-payload.md +++ b/quorum-key-management/src/generated-documents/level-2/fixed-location/proposer/create-transaction-payload.md @@ -22,7 +22,7 @@ The proposer must combine these values into a single message, which can be a sim * Ensure that the computer is configured to sign commits with the desired key. Refer to the [Appendix: Git Commit Signing Configuration](#git-commit-signing-configuration) -* Clone the [Ceremonies Repository](/generated-documents/level-2/fixed-location/provisioner/ceremonies-repository.html) for your organization to the machine +* Clone the [Ceremonies Repository](../provisioner/provision-ceremonies-repository.md) for your organization to the machine ## Procedure @@ -61,7 +61,9 @@ The proposer must combine these values into a single message, which can be a sim ## Appendix ### Git Commit Signing Configuration + {{ #include ../../../../component-documents/git-commit-signing.md:steps }} ### Generating PGP Keypair & Provisioning Smart Card + {{ #include ../../../../component-documents/openpgp-setup.md:steps-keyfork }} diff --git a/quorum-key-management/src/generated-documents/level-2/fixed-location/provisioner/pgp-key-bootstrapping.md b/quorum-key-management/src/generated-documents/level-2/fixed-location/provisioner/pgp-key-bootstrapping.md index 65ec27b..a32dd6d 100644 --- a/quorum-key-management/src/generated-documents/level-2/fixed-location/provisioner/pgp-key-bootstrapping.md +++ b/quorum-key-management/src/generated-documents/level-2/fixed-location/provisioner/pgp-key-bootstrapping.md @@ -6,14 +6,18 @@ The initial set up requires the provisioner and operator to do all of these in a * 3 individuals in order to have the flexibility for washroom breaks, fetching food and drinks etc. -* AirgapOS SD Card: [Provisioning Guide](./provision-airgapos.md) +* [AirgapOS SD Card](./provision-airgapos.md) -* Tamper Proofing Equipment: [Provisioning Guide](./provision-tamper-proofing-equipment.md) +* [Tamper Proofing Equipment](./provision-tamper-proofing-equipment.md) -* Smart Cards (whatever number of PGP keys are being provisioned): [Smart Cards](../../../../component-documents/hardware-models.md#smart-cards) +* [Smart Cards](../../../../component-documents/hardware-models.md#smart-cards) + + * 2 per PGP keypair * SD Cards: [Provisioning Guide](./provision-sd-card.md) + * 3 per PGP keypair + * Designated facility ## Procedure