[ale] ssh for automated management

[David Corbin]

On Friday 17 December 2004 13:18, Mike Murphy wrote:
> you *could* turn known hosts checking off for this, I suppose. Or use a
> single trusted hosts file instead. That would be a lot cheaper (no
> public keys).

Well, no public keys to idenitfy hosts, right?  To be honest, this client just 
doesn't seem to care about security all that much.  I'm sure they're wiliing 
to assume that the packets are going to the right machine.

>
> Mike
>
> Jim Popovitch wrote:
> > I'm wondering just how big .ssh/known_hosts will be on your mgmt
> > station.  At some point having multiple mgmt stations, or chrooted
> > environments, might make good sense.  Parsing a 3GB known_hosts file for
> > every SSH connection might present some problems.
> >
> > -Jim P.
> >
> > On Fri, 2004-12-17 at 11:56 -0500, David Corbin wrote:
> >>We are considering using ssh as part of a solution for automated remote
> >>managment of 10000+ node network, distributed at over 500 sites.  The
> >> nodes being managed are NOT "standard desktop machines" (in terms of
> >> software etc.), but more like "appliances".
> >>
> >>Ideally all the management would be done from one machine.
> >>
> >>Anyone want to suggest any likely problems we might encounter,
> >> scale-wize?
> >>
> >>Thanks
> >>David
> >>_______________________________________________
> >>Ale mailing list
> >>Ale at ale.org
> >>http://www.ale.org/mailman/listinfo/ale
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale