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
Rather than setting StrictHostKeyChecking to no or using ssh_known_hosts in addons, I would prefer explicitly specifying the fingerprint. It seems that otherwise my deployment would be susceptible to man-in-the-middle attacks.
All the searches I did came up with folks recommending disabling security, which seems rather strange.
The text was updated successfully, but these errors were encountered:
It turns out this is possible at least through creating a local known_hosts resource and using -o UserKnownHostsFile=known_hosts whenever using ssh or scp.
Rather than setting StrictHostKeyChecking to no or using ssh_known_hosts in addons, I would prefer explicitly specifying the fingerprint. It seems that otherwise my deployment would be susceptible to man-in-the-middle attacks.
All the searches I did came up with folks recommending disabling security, which seems rather strange.
The text was updated successfully, but these errors were encountered: