On Sun, Oct 23, 2011 at 13:18, Reindl Harald <h.reindl(a)thelounge.net> wrote:
Am 23.10.2011 13:09, schrieb suvayu ali:
On Sun, Oct 23, 2011 at 13:04, Reindl Harald <h.reindl(a)thelounge.net> wrote:
> Am 23.10.2011 12:58, schrieb suvayu ali:
>
>> I am no expert, I just said what worked for me in the past. I ssh into
>> many systems everyday so changing to non-standard ports is
>> inconvenient
> where is there any single problem if you can read manuals?
> you have to specify the port only once per client and after
> that rsync, ssh, scp and sftp even in konqueror is using this
> port
> Please read carefully. I ssh to *multiple* machines. The list of
> clients is hundreds, also I don't have the complete list.
well i maintain 40 machines, all with non-standard-port and connecting
multiple hundret times to omst of them each day
/home/username/.ssh/id_rsa is needed on all clients or do you really
allow password-login on standard-port and type the password all day long?
so there is supported a file called "config" in the same folder
I know about ~/.ssh/config and I use it. Logging in to the remote nodes
is not the issue in my case. I use kerberos to authenticate anyway. The
issue is when I want to access my machine from those remote nodes, I
have to copy the section relevant to my machine to the remote nodes.
I use other ways to deal with securing my system like configuring ssh to
reject hosts with more than one failed attempts, denyhosts and of course
a firewall.
> I mostly have to login to a distributed computing resource where
the
> physical node you is selected dynamically based on availability and
> load. So I don't have the complete list of IPs.
ip-addresses are not interesting here
failovers are working dns-based, so your hostname is the same
the ssh-client config is hostname-based
I know that and I use them when appropriate.
--
Suvayu
Open source is the future. It sets us free.