When processing the ~/.ssh/config file, sshtunnel appears not to act on the Include directive, to load further config from a different file. This means it uses different SSH config from the ssh command making a connection to the same server.
My set-up is generic SSH config in ~/.ssh/config, which ends with this to include further config:
Include ~/.ssh/local_config
(That's so that the first file can be copied to all computers I use, shared with others, and so on. The second file contains anything to do with specific user accounts or hosts, which varies and may be private.)
I think sshtunnel isn't using the config from the included file, so is trying to connect using the wrong username (and therefore failing). This is with version 0.4.0.
The relevant config is acted on if temporarily pasted into ~/.ssh/config itself; and it also uses it if I specify sshtunnel -c ~/.ssh/local_config — but that then obviously misses out settings from the main ~/.ssh/config file.
To reproduce:
Have somewhere to SSH to which requires a config directive, for instance a username which is different from the local username.
Put that config in its own file, and Include that file from ~/.ssh/config.
Use ssh to connect, and see that it works, taking the config from the included file.
End that connection and use sshtunnel, finding that it fails (and using a -v or 2 to see what it's doing, for instance trying the wrong username).
Move that config into the min ~/.ssh/config and verify that both ssh and sshtunnel now use it.
When processing the
~/.ssh/configfile,sshtunnelappears not to act on theIncludedirective, to load further config from a different file. This means it uses different SSH config from thesshcommand making a connection to the same server.My set-up is generic SSH config in
~/.ssh/config, which ends with this to include further config:(That's so that the first file can be copied to all computers I use, shared with others, and so on. The second file contains anything to do with specific user accounts or hosts, which varies and may be private.)
I think
sshtunnelisn't using the config from the included file, so is trying to connect using the wrong username (and therefore failing). This is with version 0.4.0.The relevant config is acted on if temporarily pasted into
~/.ssh/configitself; and it also uses it if I specifysshtunnel -c ~/.ssh/local_config— but that then obviously misses out settings from the main~/.ssh/configfile.To reproduce:
Includethat file from~/.ssh/config.sshto connect, and see that it works, taking the config from the included file.sshtunnel, finding that it fails (and using a-vor 2 to see what it's doing, for instance trying the wrong username).~/.ssh/configand verify that bothsshandsshtunnelnow use it.Please could
sshtunnelsupportInclude? Thanks.