Bug #36456
closed
Not possible to use ProxyJump or ProxyCommand for remote execution.
Description
PR https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/89 added a commmand line option "-o ProxyCommand=none" to the ssh execution. As pointed out there and discussed in https://community.theforeman.org/t/remote-execution-not-using-jump-host-bastion-host-configuration/32127/6 this effectively prevents the use of proxy hosts with ssh, as ProxyCommand on the command line takes precedence before ProxyJump/ProxyCommand in .ssh/config.
Thus, in any scenario which requires ProxyJump to access clients this won't be possible, unless a smart proxy is installed directly on the jump host.
I think instead of using command line options the configuration would better be placed into ~foreman-proxy/.ssh/config allow people to overwrite it if necessary.
Updated by Gerald Vogt about 2 years ago
- Found in Releases smart_proxy_remote_execution_ssh-0.9.0 added
- Found in Releases deleted (
foreman_remote_execution-8.2.0)
Updated by The Foreman Bot 9 months ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/117 added
Updated by The Foreman Bot 9 months ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.11.1 added
Updated by
Updated by Adam Ruzicka 8 months ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.11.3 added
- Fixed in Releases deleted (
smart_proxy_remote_execution_ssh-0.11.1)