Project

General

Profile

Actions
Copy link

Bug #36456

closed

Not possible to use ProxyJump or ProxyCommand for remote execution.

Added by Gerald Vogt over 1 year ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/117
Fixed in Releases:
smart_proxy_remote_execution_ssh-0.11.3
Found in Releases:
smart_proxy_remote_execution_ssh-0.9.0
Red Hat JIRA:

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.

Actions
Copy link

Also available in: Atom PDF