Documentation: Expand instructions for Certificate Authority setup #841
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
|
These are some links that could be useful in the instructions, but I omitted them to keep the documentation brief, and also free from hand-waving solutions to untested resources. |
notevenaperson
changed the title
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.
Motivation and Context
I found the documentation for using pywb Certificate Authority difficult to use for adding the CA to Chromium, as I had never done something like that before. I attempted to make the 4th step as clear as possible, "4. You may need to agree to "Trust this CA" to identify websites." (Agree where?) Also, the ordering of the paragraphs was somewhat disjointed.