Reputation: 7232
When connecting to an AWS instance via ssh using -
ssh -i "key.pem" <aws-instance>
A message in the terminal reads -
The authenticity of host <host> can't be established
Now, generally I am ignoring it and going to the next step to add the key fingerprint and then successfully ssh into the server. But I am curious to know what are some of the potential pitfalls that this authenticity issue can lead to?
Upvotes: 1
Views: 1706
Reputation: 7232
From the comment section by @Amaden:
SuperUser: Are SSL's default snake oil certificates truly snake oil as opposed to being genuine honest-to-good certificates? explains it well: since the certificate isn't chained to well-known certificate authority, you can't know that the server is who you think it is (as opposed to someone else impersonating the server). As one answer says, these days it is trivial (and free) to create a trusted certificate, which will remove the trust issue (and the warning).
Upvotes: 1