On Thursday 05 April 2007 08:29, Alok G. Singh wrote: > On 29 Mar 2007, [EMAIL PROTECTED] wrote: > >> The scenario is simple. I have a setup with port forwarding, > >> where my ssh client thinks am connecting to a different host > >> each time. ( ip remains same, port is different on ssh > >> commandline ) and its a hassle to delete the "cached" line from > >> the known_hosts everytime. > > > > man ssh_config , look at the UserKnownHostsFile directive. Set > > it to /dev/null in the config file or on the ssh command line. > > madduck had a useful post about this recently [1]. CheckHostIP and > StrictHostkeyChecking are essential in guaranteeing a secure > connection and global disabling of them will just give you a false > sense of security.
...and do you have a better method of solving his problem? In any case he has to manually validate the key that the server presents each time he connects to it; I don't see how not storing that key (which is what I recommended) will impact his security any further. Regards, -- Raju -- Raj Mathur [EMAIL PROTECTED] http://kandalaya.org/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F It is the mind that moves ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-india-help mailing list linux-india-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-india-help
