Start9/documentation
2
0
Fork 0
mirror of https://github.com/Start9Labs/documentation.git synced 2026-03-26 02:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix/add ssh tofu warning (#589)

Browse Source 
* Add SSH pubkey warning on first ssh connection

* Clarify instructions
This commit is contained in:
gStart9
2024-01-23 16:44:31 +00:00
committed by GitHub
parent dc07a6900d
commit 79241e7c65
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
site/source/user-manual/ssh.rst
View File

@@ -100,7 +100,20 @@ Connecting via CLI
Replacing ``<SERVER-HOSTNAME>`` with your server's LAN (``<custom-address>.local``) address Replacing ``<SERVER-HOSTNAME>`` with your server's LAN (``<custom-address>.local``) address
.. note:: If you get a scary looking warning that says something like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" - fear not! This is most likely happening because you have recently reflashed or did an update from pre-v0.3.3, which would cause a change in the key for your device's hostname (e.g. `xxxxxxxx.local`) or IP address (e.g. `192.168.1.x`). The solution is to delete the existing entry from your `known_hosts` file, which is typically located at `~/.ssh/known_hosts`. This will be specified in the warning, along with a helpful line number (in case your file is lengthy). .. note::
The first time you connect, you will see something like this:
``The authenticity of host 'pregame-margin.local (192.168.1.175)' can't be established.``
``ED25519 key fingerprint is SHA256:BgYhzyIDbshm3annI1cfySd8C4/lh6Gfk2Oi3FdIVAa.``
``This key is not known by any other names.``
``Are you sure you want to continue connecting (yes/no/[fingerprint])?``
Type ``yes`` and hit Enter to start trusting the server's SSH public key.
If you get a scary looking warning that says something like ``WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!`` - fear not! This is most likely happening because you have recently reflashed or did an update from pre-v0.3.3, which would cause a change in the key for your device's hostname (e.g. `xxxxxxxx.local`) or IP address (e.g. `192.168.1.x`). The solution is to delete the existing entry from your `known_hosts` file, which is typically located at `~/.ssh/known_hosts`. This will be specified in the warning, along with a helpful line number (in case your file is lengthy).
Connecting via PuTTY on Windows Connecting via PuTTY on Windows
------------------------------- -------------------------------