On 14/10/11 12:24 PM, Hart, Michael wrote: > Francois my Hero! :) > > That did the trick. I had to do some editing on the /root/.ssh/known_host > files first to delete some of the information from our original work over a > year ago. But after that it was clear sailing. > > <In by most annoying whiny voice> > But I have almost 700 Devices on my networks! You mean I will have to > repeat this process for each of those devices? > <end of whining > > > Something tells me I have some new script writing in my future, or I will be > giving my 1 assistant a very boring and tedious job :) >
It can be done quite simply with an ssh config file. I never took the time to document it but now I just did for you: http://www.packetfence.org/support/faqs/article/is-there-a-way-to-avoid-host-key-verification-on-every-ssh-based-network-devices.html This should save you time. -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
