Repository navigation
docs(install-deploy): show the sign-a-downloaded-ISO command and its outputs - #135
Merged
Merged
Conversation
…outputs The "Download the unsigned image" section told readers to sign a release asset with cryptosctl image sign but only linked out for the command itself. Every other build path on this page (signed build, unsigned build) shows the actual command and the files it writes, so this one now does too: the --image/--key/--cert invocation and the signed ISO, UKI and .sig it leaves next to the input. Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What and why
docs/install-deploy/build-bootable-image.md's "Download the unsigned image"section told readers to sign a downloaded release asset with
cryptosctl image signbut only linked out tocryptos-node's doc for thecommand itself, unlike every other build path on this page (the signed build
and the unsigned build both show the actual command and a table of the files
it writes). This adds that: the
--image/--key/--certinvocation againsta downloaded unsigned ISO, and the three files it leaves beside the input
(the signed ISO, the signed
.uki, and the.uki.sigcryptosctl image stagesends for later upgrades), matching
cryptos-node'sdocs/image-sign.mdandcryptos-appliance'sdocs/secure-boot.md, which are the source for thiscommand.
docs/install-deploy/secure-boot.mdalready points at this section by anchor(
#download-the-unsigned-image) for the same path, and that anchor isunchanged, so it needed no edit.
Refs CryptOS-PKI/cryptos-appliance#83
Verification
How this was verified
This is a docs-only change to one existing section; I don't build the site on
this box. CI (
npm ci && npm run build, which renders the whole site) is theproof. Read the rendered Markdown by eye against the page's existing sections
for list and code-fence indentation, and checked that the anchor
secure-boot.mdlinks against (#download-the-unsigned-image) still matchesthe unchanged heading.