ssh: add explicit host filter before SendEnv #115
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
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.
The
SendEnvsetting here is assuming there isn't some otherHostfilters inprograms.ssh.extraConfigthat will appear before it, but that wasn't the case on my systems, as I have some host-specific configuration included. AddingHost *beforeSendEnvwill ensure that no matter where it appears, it will still apply to all hosts.Without this, the VNC proxy to other nodes in the cluster was failing because it wasn't sending the ticket along in the
LC_PVE_TICKETenv var.