Minor doc update: Clarify client is creating the public private key pair in 'How Sigsto… #359
Conversation
This file contains 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
✅ Deploy Preview for docssigstore ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Can you sign the DCO? |
…re works' section of overview. Signed-off-by: Sam Pinkus <[email protected]>
Done! |
haydentherapper
approved these changes
Jan 23, 2025
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.
…re works' section of overview.
Summary
Was briefly confused about what the responsibilities of Fulcio and the client are and got the stupid idea in head that maybe Fulcio is generating a public/private key pair. But it's just regular x509 CA and CSRs ... The change just adds detail to make that clearer.
Release Note
NONE.
Documentation
This change is documentation. Does not require documentation.