Open RanceH opened 2 years ago
Possibly a duplicate of https://github.com/Eugeny/tabby/issues/5559? The config parsing might not be supporting all of the features just yet.
After reading the issue posted in 5559 I agree that these can be considered duplicates. Both are related to ssh config file parsing.
I don't see how to close this ticket and link it to 5559 as a duplicate so that the use cases don't get lost when the ssh config parser work is done.
Please close as a dupe.
The translator bot has detected that this issue body's language is not English, and has translated it automatically.
Please close as a dupe.
Brand new Tabby user here, downloaded latest version and installed on my Mac OS 12.6 Monterey laptop for testing.
I seem to be having an issue with profiles imported from my ~/.ssh/config file.
Background
I have in my .ssh/config file each host that I normally connect with listed multiple times with different alias names to compensate for being remote or local to the box that I am ssh-ing into.
Example config:
Host homeproxy Hostname fqdn
Host *.home ProxyJump homeproxy
Host desk Hostname desk.private
Host desk.home HostName desk.private
The theory here is that if I'm at home I can directly connect to the box desk, as I'm on its network already, but if I'm at the office, I have to use the proxy jump, so all I have to do is ssh to desk.home and the proxy instruction is used.
Tabby discovers all these entries in my config, and lists them each as a profile option, but if you click on desk.home it doesn't connect properly cause it doesn't understand the proxy jump.
opening a conventional shell session and ssh-ing to desk.home works correctly even inside tabby.
Issues:
Since the ssh stanza for *.home isn't an intended direct ssh target tabby should ignore it, but how would tabby know to do that?
Tabby's built in ssh client doesn't appear to read and follow a .ssh/config file correctly.
I realize that I may be missing something, but nothing I read came close to this scenario.