User Tools

Site Tools


ssh_keys_issue

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
ssh_keys_issue [2016/08/03 21:09] walkeradminssh_keys_issue [2017/01/12 20:12] walkeradmin
Line 1: Line 1:
 ====== SSH Keys Issue ====== ====== SSH Keys Issue ======
 +<color darkorange>2016</color>
 +\\ 
 \\  \\ 
 \\  \\ 
Line 7: Line 9:
     ECDSA key fingerprint is 65:76:dc:ba:74:d6:c7:75:7f:21:58:c6:66:42:23:7d.     ECDSA key fingerprint is 65:76:dc:ba:74:d6:c7:75:7f:21:58:c6:66:42:23:7d.
 \\  \\ 
-    Just SSH to the machine from the command line and your key will be added to the target host.  +\\ You need to add your key to the remote device to be trusted, then you won't get asked for password on each connection (a real pain when using scripts). 
-    You only need to do this once.+\\  
 +\\  
 +===== This Worked for Us in the End ===== 
 +\\  
 +\\  
 +From the command line:\\  
 +\\  
 +    ssh-keygen 
 +     
 +    Press enter for every prompt 
 +     
 +    This will place your local key in the remote server 
 +\\  
 +\\  
 +Then run this: 
 +\\  
 +    ssh-copy-id -i ~/.ssh/id_rsa.pub 192.168.1.10 
 +     
 +    Enter the remote server password 
 +\\  
 +Now you should be able to ssh to the server without a password
 \\  \\ 
 +    ssh ipaddress
 \\  \\ 
-    Warning: Permanently added '192.168.1.11' (ECDSA) to the list of known hosts. 
 \\  \\ 
ssh_keys_issue.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1