4 ms·

The authenticity of host 'terminal.shop (172.65.113.113)' can't be established. ED25519 key fingerprint is SHA256:TMZnO7N8mmR/Pap3urU2P4uBNuhxuWtDUak0g9gyZ8s T

• zaik 3y ago
  Have you added the required line to ~/.ssh/known_hosts as described on their website?
  • cgriswald 3y ago
    That's not actually what they describe. They describe catting known_hosts and seeing terminal.shop with the given key in the output. That won't work if you don't continue to connect because known_hosts won't be updated with their key. Additionally, if hosts are hashed, you won't see terminal.shop anyway.
    • zaik 3y ago
      I think what "cat" here means is that you are supposed to add their key to the known hosts file manually before you connect. Showing the output of "cat file" is a way of saying "this should be in the file".
      • cgriswald 3y ago
        I think it’s fair if they want to assume a certain competence from their audience, and they’re being cute. But these aren’t instructions and if they are, well, the ssh command happens first.
• tichiian 3y ago
  No. The key listed is the whole plain ed25519 pubkey (those are relatively short). The message displays the SHA256 digest. You can check that in your local known_hosts file (after having connected at least once) with "ssh-keygen -F terminal.shop -l" and "ssh-keygen -F terminal.shop -lv". (Yes, it is confusing that the command is named "ssh-keygen" but does lots of things that are not about generating any keys) If you want to do it without connecting, try "ssh-keyscan terminal.shop".
• deleted 3y ago
  [deleted]