[Bug]: Sysinfo for remote servers with Proxy

[safaci2000]

Current Behavior

I have several SSH hosts I need to go through a Proxy an example of my ssh_config is listed below:

Host staging
    Hostname staging.foobar.net
    ForwardAgent yes
    ProxyCommand ssh -q -W %h:%p jump

Host jump
    Hostname jump.foobar.net

The issue is that the supported hosts listed in sysinfo show all the know hosts configured in my ~/.ssh/config but none of them are reachable since it ignores the ProxyCommand.

ssh staging does work from the terminal but the wave UI doesn't seem to know how to handle that option

Expected Behavior

sysinfo data to be displayed from the remote host.

Steps To Reproduce

Configure any host with a ProxyCommand setup in your $HOME/.ssh/config

Wave Version

v0.11.0

Platform

macOS

OS Version/Distribution

OS X 15.2

Architecture

arm64

Anything else?

No response

Questionnaire

• I'm interested in fixing this myself but don't know where to start
• I would like to fix and I have a solution
• I don't have time to fix this right now, but maybe later

[esimkowitz]

We don't currently support ProxyCommand for WSH connections, are you not able to use ProxyJump?

[safaci2000]

I think there's too many factors involved that it doesn't like. Proxyjump works but I also have an ssh-agent running that loads my credentials to authenticate.

If I use:

Host staging
    Hostname staging.foobar.net
    ForwardAgent yes
    ProxyJump jump

If I ssh with the updated configuration, simple ssh works fine. When I try to use wave, it prompts me for a password rather than using the ssh-key provided.

Let's call it a nice to have features, but I recognize this might be a bit of an edge case ask.

[esimkowitz]

What's requesting a password? Your agent or one of your keys?

[esimkowitz]

If you don't want to use a key from your agent you can pass IdentitiesOnly

[safaci2000]

I do want to use the key from the agent, that's the issue, it wasn't using the same pattern as the standard ssh client. I also tried using IdentitiesOnly and that didn't seem work any better. Actually setting IdentitiesOnly seems to break my ssh.

ssh-add -l

2048 SHA256:/HashID L4 User Credential (RSA)