15 Mar
2010
15 Mar
'10
4 p.m.
** john lewis <zen57162(a)zen.co.uk> [2010-03-15 13:15]:
** end quote [john lewis]
Not wanting to state the obvious, but are you using the -p switch when
connecting? eg:
ssh -p 26 myhost.mydomain.com
if you've moved to port 26 by adjusting the port line in /etc/ssh/sshd_config:
Port 26
to make things more convenient you can create a file in ~/.ssh called config to
set default settings, so:
Host myhost
Hostname myhost.mydomain.com
Port 26
User john
IdentityFile ~/.ssh/id_rsa
would allow you to use:
ssh myhost
and automatically use the correct port to get to the server, as well as start
the login with the user john and appropriate key file.
Sorry if that's all obvious :)
--
Paul Tansom | Aptanet Ltd. | http://www.aptanet.com/ | 023 9238 0001
======================================================================
Registered in England | Company No: 4905028 | Registered Office:
Crawford House, Hambledon Road, Denmead, Waterlooville, Hants, PO7 6NU
On Mon, 15 Mar 2010 11:37:35 +0000
Paul Tansom <paul(a)aptanet.com> wrote:
> ** Andy Smith <andy(a)bitfolk.com> [2010-03-14 16:22]:
> > This very long email is about possible pro-active measures I could
> > take to prevent customers being compromised by SSH dictionary
> > attacks. The first part is just a recap of how we got here and what
> > happens. If you want to make it shorter by skipping that, then skip
> > to line 59 which begins with "Being compromised by an SSH dictionary
> > attack..."
> <snip>
<snip>
> 6) Move
sshd to another port.
I thought to do that as well but found it wasn't just a matter of
changing the port from 22 to summat else in /etc/ssh/sshd_config as I
couldn't then ssh in when I tested it from another terminal getting an
'unable to open port 22' error.