Bash>ssh> ports>?

[pclinmike]

If I change 'ssh' ports to say 2222 in pcc how do I tell 'Bash' ?, it still wants to use port 22 for ssh !.

eg.

[root@localhost ~]# ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155



ssh: connect to host 192.168.0.155 port 22: Connection refused

Now try logging into the machine, with "ssh 'root@192.168.0.155'", and check in:

  .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

[muungwana]

try:
ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155:2222

[pclinmike]

try:
ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155:2222

root@localhost ~]# ssh ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155:2222
ssh: Could not resolve hostname ssh-copy-id: Name or service not known

[pags]

Looks like ssh-copy-id is a script that simplifies copying the keys to a remote authorized_keys file...you could do it manually (it's a one time exercise per client).  Either by ssh'ing into the remote PC and adding the value, or by pulling the file over to your local machine, editing it and putting it back (use scp, for that).

Doesn't look like the script includes any provision to change the default ssh port.

[TerryN]

try:
ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155:2222

root@localhost ~]# ssh ssh-copy-id -i .ssh/id_rsa.pub root@192.168.0.155:2222
ssh: Could not resolve hostname ssh-copy-id: Name or service not known

Err... you seem to have inserted an extra "ssh" in there  

The result is that ssh-copy-id becomes a "hostname" argument which, of course, does not exist

The important point is that if you have a service running on a non-standard port you specify it by appending the port to the address or hostname with a ":"  
For example:  192.168.0.155:2222

Terry

[ghostbunny]

why didn't you use ssh --help ?

you will find the option -p