Displaying 3 results from an estimated 3 matches for "bigcustomer".
2023 Aug 18
1
Host key verification (known_hosts) with ProxyJump/ProxyCommand
...t repo):
Include /home/me/workplace/ops/config/ssh/prod/*
Include /home/me/workplace/ops/config/ssh/dev/*
Include /home/me/workplace/ops/eng-ssh/*-config
So assuming one of those files was
/home/me/workplace/ops/eng-ssh/bigcust-config
# Bastion router on the site, VPNing back to the office
Host bigcustomer-00123-bne-md01
HostName 10.20.34.5
UserKnownHostsFile bigcustomer-00123-bne-md01-hosts
Host bigcustomer-00123-bne-br01
HostName 172.30.0.100
ProxyJump user at bigcustomer-00123-bne-md01
UserKnownHostsFile bigcustomer-00123-bne-md01-hosts
Host bigcustomer-00123-bne-md...
2023 Aug 18
2
Host key verification (known_hosts) with ProxyJump/ProxyCommand
On 18.08.23 07:39, Darren Tucker wrote:
> On Fri, 18 Aug 2023 at 15:25, Stuart Longland VK4MSL <me at vk4msl.com> wrote:
> [...]
>> The crux of this is that we cannot assume the local IPv4 address is
>> unique, since it's not (and in many cases, not even static).
>
> If the IP address is not significant, you can tell ssh to not record
> them ("CheckHostIP
2023 Aug 18
1
Host key verification (known_hosts) with ProxyJump/ProxyCommand
On 19/8/23 08:00, Stuart Longland VK4MSL wrote:
> Would the UserKnownHostsFile be relative to the current working
> directory of the `ssh` process at the time of its call, or would it
> figure out that these files are relative to
> /home/me/workplace/ops/eng-ssh/bigcust-config?
Nope? just tried it, at this time it's relative to whatever directory
you call `ssh` from.
Which if