On Wed, Jun 23, 2010 at 7:38 PM, Paul McNett <[email protected]> wrote: > >> 3. Don't you need to register your server's public key on your client >> via something like this or is this an optional step? >> >> cat your-server_dsa.pub>> /home/Administrator/.ssh/known_hosts file > > SSH does that automatically (actually, it prompts you first). So yeah, you > can go out > of your way to do that if you want, or just let SSH do it for you. >
Just to emphasize that point (as I've wasted hours trying to debug it when it wasn't broke): Even if you're only planning to use rsync to transfer files, run ssh first once, and you'll get a confirmation message, paraphrasing, ssh -p 8822 example.com The authenticity of host '[example.com]:8822 ([123.222.111.99]:8822)' can't be established. RSA key fingerprint is d0:1f:47:b2:7c:67:2c:2c:e5:9f:cd:26:28:cd:bc:ed. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[example.com]:8822' (RSA) to the list of known hosts. Last login: Tue Jun 22 15:39:25 2010 from the.previous.host.com Without that first confirmation, rsync may fail if ssh is configured to only connect to known hosts, a nice security feature. But not always easy to debug. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
