-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remember to document RSA host key in any place... #34
Comments
ssh-keygen -f "/home/teo/.ssh/known_hosts" -R manipulation
|
(Private ssh keys are meant to be... private.)
|
@PeterBowman is right |
😑 😑 😑 😑 😑 😑 |
I guess the best thing to do is to create a new one (and keep it private) 😉 |
Obviously it's good to keep good security practices, but since we are in a LAN, I think we don't have to be extremely paranoid. Based on this, and to be practical, I think it's okay to not consider a man-in-the-middle attack and simply erase the RSA key associated to Please correct me guys if I'm saying something terribly misguided. |
@jgvictores I am totally agree with you. I tried to change the default password assigned in Ubuntu for the one I had already registered in Debian 6 to avoid possible future problems. I know that to reveal a password in a public place like this is a mistake, but I thought that we are connected in a local network, free of dangerous hackers trying to get into Teo (or maybe yes..) and I am always trying to document all the steps or changes that are performed with the intention that another person can configure it in the future. |
It has generated a new RSA key (reinstalling openssh-server) and now the solution is erase the RSA key associated to manipulation (via ssh-keygen -f "/home/teo/.ssh/known_hosts" -R manipulation) each time we boot it on a different distro (and the same with locomotion). teo@oliver:~$ ssh-keygen -f "/home/teo/.ssh/known_hosts" -R locomotion
# Host locomotion found: line 4 type RSA
/home/teo/.ssh/known_hosts updated.
Original contents retained as /home/teo/.ssh/known_hosts.old
teo@oliver:~$ ssh locomotion
The authenticity of host 'locomotion (2.2.2.52)' can't be established.
ECDSA key fingerprint is ??:??:??:??:??:??:??:??:??:??:??:??:??:??:??:??.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'locomotion' (ECDSA) to the list of known hosts.
Warning: the ECDSA host key for 'locomotion' differs from the key for the IP address '2.2.2.52'
Offending key for IP in /home/teo/.ssh/known_hosts:4
Are you sure you want to continue connecting (yes/no)? yes
teo@locomotion's password:
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-31-generic i686)
* Documentation: https://help.ubuntu.com/
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
teo@locomotion:~$ So, I'll close this issue |
Error connecting by ssh to a new ubuntu distribution (or a new installation)
Remember to document steps to configure the ssh server (in case it was necessary) :
/etc/ssh/ssh_host_rsa_key
(with sudo)The text was updated successfully, but these errors were encountered: