You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very common access pattern for cloud environments is to set up a bastion server as the central SSH login gateway. This is a handy and growing pattern, especially within AWS Environments.
Consider the following SSH Config. This both tunnels my connection through an intermediary SSH server and forwards my ssh agent context on to it, allowing secure key exchange with the destination server, without storing my private key on the intermediary.
We NEED this facility. Having paid $40 for MountainDuck (great name!) I'd hope to see richer ssh config options soon.
You are building tools for the power users, after all :)
BONUS: Support known_hosts directives, to make dealing with ephemeral servers that have persistent hostnames more palatable!
Host *.dev.mydomain.com
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
The text was updated successfully, but these errors were encountered:
I see that there was another ticket out there. Sorry for the duplicate. I also did review the list of supported options, they just aren't rich enough for my needs.
One thing that is not mentioned in that other ticket is the AgentForwarding bit, which is crucial to the security pattern of bastion or jumpbox setup. I'll add that comment to the winning ticket.
I see that there was another ticket out there. Sorry for the duplicate. I also did review the list of supported options, they just aren't rich enough for my needs.
One thing that is not mentioned in that other ticket is the AgentForwarding bit, which is crucial to the security pattern of bastion or jumpbox setup. I'll add that comment to the winning ticket.
Great, thanks for your input!
Also, for clarity, was just being cheeky with my $40 comment. I really really REALLY love Cyberduck, have been using it for over a decade with pleasure and much gratitude. I'm very glad to be supporting the project and all it's efforts!
A very common access pattern for cloud environments is to set up a bastion server as the central SSH login gateway. This is a handy and growing pattern, especially within AWS Environments.
Consider the following SSH Config. This both tunnels my connection through an intermediary SSH server and forwards my ssh agent context on to it, allowing secure key exchange with the destination server, without storing my private key on the intermediary.
We NEED this facility. Having paid $40 for MountainDuck (great name!) I'd hope to see richer ssh config options soon.
You are building tools for the power users, after all :)
BONUS: Support known_hosts directives, to make dealing with ephemeral servers that have persistent hostnames more palatable!
The text was updated successfully, but these errors were encountered: