|
Posted by Chuck on June 12, 2006, 3:28 pm
If you were Registered and logged in, you could reply and use other advanced thread options Robert wrote:
> On Wed, 07 Jun 2006 02:06:31 +0100, Tristan Miller wrote:
>
>> Greetings.
>>
>> Most of the time my computers are behind a router/firewall that blocks port
>> 22, but occasionally I unblock it if I'm going somewhere and need to log
>> into my machines remotely. Whenever I do this I notice in
>> my /var/log/messages that some script kiddie is repeatedly connecting via
>> ssh and trying to guess usernames. The IP changes every time so I'm not
>> sure if it's just one guy using hijacked machines or different people.
>
> I see as you have a few options;
>
> 1. Use Key-login
> 2. Use a different port
> 3. Use IPTABLES to block all connections after x number of failed
> connections.
>
> It would be best to use all 3 of these options and then you would really
> be securing your system.
>
>
FYI I am running my ssh server on a nonstandard port (way up high), and
set the only authentication method allowed to be PubkeyAuthentication.
In 6 months with this config, not one break in attempt has been detected.
|