Make the OpenSSH guide more usable #12183
Merged
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
|
would be good to add that the output of below can be added to $ tctl auth export --type=user |
ptgott
force-pushed
the
paul.gottschling/11841-7
branch
from
0a9e42a to
889b485
Compare
|
@stevenGravy Thanks! I finally got this to work using the instructions in the original guide (modified a bit), and I can make time to incorporate the |
ptgott
force-pushed
the
paul.gottschling/11841-7
branch
from
889b485 to
fb6496c
Compare
strideynet
reviewed
May 18, 2022
strideynet
approved these changes
May 20, 2022
ptgott
force-pushed
the
paul.gottschling/11841-7
branch
from
ab1f027 to
be0fced
Compare
zmb3
approved these changes
Jun 3, 2022
See #11841 - Add a Prerequisites section and divide the instructions into steps via H2 headings. - Use ScopedBlocks to add instructions for Cloud users. - Fill in missing instructions (e.g., adding host_cert permissions for Cloud users and editing the file permission of the host key/cert) - Since all supported versions of Teleport now include "tsh config," remove the manual OpenSSH configuration option. This makes the guide much simpler to follow. - Add a Details box explaining "tsh config" The original OpenSSH guide included some technical details about the proxy subsystem, but without enough context to understand the configuration generated by tsh config. I've moved the technical details into a Details box, and expanded them, so readers interested in how the local SSH config they generate via "tsh config" works. - Indicate that you need to specify the SSH port when connecting to an OpenSSH host via configuration generated by tsh config.
ptgott
force-pushed
the
paul.gottschling/11841-7
branch
from
be0fced to
7a21445
Compare
This was referenced Jun 6, 2022
ptgott
added a commit
that referenced
this pull request
Jun 7, 2022
* Make the OpenSSH guide more usable See #11841 - Add a Prerequisites section and divide the instructions into steps via H2 headings. - Use ScopedBlocks to add instructions for Cloud users. - Fill in missing instructions (e.g., adding host_cert permissions for Cloud users and editing the file permission of the host key/cert) - Since all supported versions of Teleport now include "tsh config," remove the manual OpenSSH configuration option. This makes the guide much simpler to follow. - Add a Details box explaining "tsh config" The original OpenSSH guide included some technical details about the proxy subsystem, but without enough context to understand the configuration generated by tsh config. I've moved the technical details into a Details box, and expanded them, so readers interested in how the local SSH config they generate via "tsh config" works. - Indicate that you need to specify the SSH port when connecting to an OpenSSH host via configuration generated by tsh config. * Respond to PR feedback
ptgott
added a commit
that referenced
this pull request
Jun 8, 2022
* Make the OpenSSH guide more usable See #11841 - Add a Prerequisites section and divide the instructions into steps via H2 headings. - Use ScopedBlocks to add instructions for Cloud users. - Fill in missing instructions (e.g., adding host_cert permissions for Cloud users and editing the file permission of the host key/cert) - Since all supported versions of Teleport now include "tsh config," remove the manual OpenSSH configuration option. This makes the guide much simpler to follow. - Add a Details box explaining "tsh config" The original OpenSSH guide included some technical details about the proxy subsystem, but without enough context to understand the configuration generated by tsh config. I've moved the technical details into a Details box, and expanded them, so readers interested in how the local SSH config they generate via "tsh config" works. - Indicate that you need to specify the SSH port when connecting to an OpenSSH host via configuration generated by tsh config. * Respond to PR feedback
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.
See #11841
H2 headings.
Cloud users and editing the file permission of the host key/cert)
remove the manual OpenSSH configuration option. This makes the guide
much simpler to follow.
included some technical details about the proxy subsystem, but
without enough context to understand the configuration generated by
tsh config. I've moved the technical details into a Details box, and
expanded them, so readers interested in how the local SSH config they
generate via "tsh config" works.