Don't load ForwardedPorts from the .tsh/profile #26823
Merged
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.
This was leading to unexpected behavior where tsh was implicitly forwarding ports when running
tsh ssh
and would make it so a user could not runtsh ssh
multiple times simultaneously due to conflicting ports already being open.With this change ports to forward must always be explicitly passed via the
-L
flag.Fix for #3094 and https://github.com/gravitational/customer-sensitive-requests/issues/69.