I have a application server that can be deployed only via a SSH jump host.
However, the feature updating SSH known hosts in the Pipelines seems to support only hosts accessible directly from the internet.
How can I fetch the SSH host key of servers behind jump hosts?
To which feature of updating SSH known hosts in the Pipelines are you referring to? Can you provide a link? I just ask b/c it's not very clear to me which makes it hard to give concrete suggestions.
If you update known hosts unattended w/o providing a known good, this basically means that you ignore it anyway. If that is the case, you can disable the check / dev/null the known hosts file and disable the warning (StrictHostKeyChecking and UserKnownHostsFile options). This would be by SSH settings.
Still yet I can't say from your question which SSH options are accessible in your scenario. This can be done in the SSH config file or on the command line (e.g. ProxyCommand option).
But perhaps this helps you already.
I can connect to the host only by `ssh target` the following SSH configuration (sensitive information is replaced)
Assume hosts of *.localnetwork.mydomain.example.snip can't be accessed directly from outside of *.mydomain.example.snip . Pipeline containers can access to ssh-jumphost.mydomain.example.snip .
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events