Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: SSH with a central host list?

Subject: Re: SSH with a central host list?
Date: Fri, 14 Jan 2005 21:15:28 +0200 (IST)
On Thu, 13 Jan 2005, John Horne wrote:
Our networking team are using secure shell to access their network
devices from Windows XP laptops. However, at present there are over 400
devices and each member of the team has their own copy of those devices
DNS name and/or IP address in a list. The problem is that whenever a
device is changed (IP address), added or removed then each member of the
team has to be told and update their list. This does not work well!

I have been asked to see if there is a secure shell client, be it open
source, shareware, commercial or whatever, that supports some form of
'central host list'. Ideally this would be just a text list of DNS names
held on a central file store. That way the team only has to update one
list and the change is then immediately accessible to all team members.

Don't sure that I really understand your question.

If only IP addresses change then you can use simple DNS server to
store domain -> ip mapping (both domain names and IPs can be private,
i.e. device1.localdomain. and 10.0.1.5). In fact, it is exactly the
purpose of DNS as opposed to hosts files.

If some other config info has to be changable (e.g., ssh ports) then
you can share your config using configuration file which could be
updated (e.g., you can download it from some internal http server on
each boot, or use a file on some SMB share). The name of the
configuration file is different for each ssh client...

-- 
Regards,
ASK

<Prev in Thread] Current Thread [Next in Thread>