Implement ssh --forward-agent | -x functionality #521
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 pull request addresses and resolves issue #252 by implementing the capability to enable SSH agent forwarding during an SSH session, with the egress key added to the agent.
The behavior is controlled by the
sshAddKeysToAgentAllowed
configuration option in bastion.conf, which is set tofalse
by default. When this option is explicitly set totrue
, users can request SSH agent forwarding by including either the--forward-agent
or-x
argument on egress SSH sessions:This enhancement provides users with greater flexibility while maintaining the secure default settings and addresses the exact scenario described in #252.
Tests have been added in its own file, as I couldn't really find a more appropriate location to add the tests.