-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jim lawrence wrote:
| I got it !!! firewall on desktop Pc was causing the issue Now | when i exit the terminal will it terminate the connection? Also i | supose i could create a script to create this connection automatically | for me? | | [jim@JimsNotebook ~]$ ssh jim@xxxxxxxxxxxx | The authenticity of host '192.168.1.50 (192.168.1.50)' can't be established. | RSA key fingerprint is XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | Are you sure you want to continue connecting (yes/no)? yes | Warning: Permanently added '192.168.1.50' (RSA) to the list of known hosts. | jim@xxxxxxxxxxxx's password: | Last login: Wed Mar 30 10:20:51 2005 | [jim@jimsdesktop ~]$ | | Why the can't be established ?
This is a one-off the first time you use ssh with a given remote machine. Your machine keeps track of a cryptographic fingerprint that belongs to the given server (have a look in ~/.ssh/known_hosts). If one day you ssh to that machine and the fingerprint is different, you get a big warning and the connection is terminated. The reason for this is it can mean someone has tricked you into connecting to an evil machine instead of the one you think you're connecting to, by poisoning your DNS or messing with ARP or whatever. It's not likely to happen for two machines in the same room, but it could happen so ssh protects against it like this.
You'll also see this if you ever reinstall the OS on the server you're connecting to, it will have a different, random fingerprint after that too.
Anyway, you won't see the "authenticity" error above again for that machine because your machine has remembered the fingerprint that belongs to that IP address.
- -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFCUZ/PjKeDCxMJCTIRAswKAJ9MvOewKxbnLGMwyoth3OovvgeUkwCfZVyI J48he4lBSknNMCChz3cwSzs= =9hRa -----END PGP SIGNATURE-----
