I am looking at different samples for configuring ssh config to support Bastion connection to my cloud's internal servers.
I'v hae encountered several (working) samples having the prefix "mux-" on the ControlPath configuration -
#ssh_config #use with ssh -F ssh_config user@<TARGET_SERVER_IP> Host * ServerAliveInterval 60 TCPKeepAlive yes ProxyCommand ssh -q -A gmasgras@<JUMP_SERVER_IP> nc %h %p ControlMaster auto ControlPath ~/.ssh/mux-%r@%h:%p ControlPersist 8h User ubuntu StrictHostKeyChecking no
I can't find any explanation regarding the
"mux-" prefix, along with the
%r@%h:%p suffix (%r=remote user, %h=host, %p=port). The combination is clearly not an actual ssh public key in the ssh folder.
In other sample ControlPath variations, people are also using:
Can you provide an explanation for the prefix convention? (