Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
How do I validate the ECDSA key fingerprint of my newly-created Droplet?
The first time I connect to a newly-created Droplet, I expect to be able to validate that the ECDSA key fingerprint is valid before adding it to my known_hosts file. I have not been able to find this information on the forum, how-to’s, or in the web console.
I’ve read through How To Connect To Your Droplet with SSH, and the DO moderator surprisingly recommends disregarding the possibility of a man-in-the-middle attack and blindly accepting the key. The actual statement is as follows: “The first time you attempt to connect to your server, you will likely see a warning that looks like this… The authenticity of host ‘126.96.36.199 (188.8.131.52)’ can’t be established… Go ahead and type yes to continue to connect. Here, your computer is telling you that the remote server is not recognized. Since this is your first time connecting, this is completely expected.” I agree that it’s expected. However, I don’t agree that that means it’s safe to assume that the connection is not compromised.
Back to my question then: Is there any way to validate the host’s fingerprint before connecting? Ideally it would be part of the response body when a new droplet is created or have its own API call.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×