SSH hacked?

[Brett Lumsden]

Or if you are worried, just slow them down / annoy them by  
implementing something like sshblack :  
http://www.pettingers.org/code/sshblack.html

Quoting "Beau J. Bechdol" <bbechdol at gmail.com>:

> I don't believe it is a silly practice, it is a good idea in my opinion.
> Another thing to consider would to setup port forwarding on the router so
> for example, when someone sends a ssh request to port 22, the router will
> froward it to the port you designated, port 2222 for example.
>
> -Beau
>
>
> On Mon, Jan 12, 2009 at 6:56 PM, Kent Borg <kentborg at borg.org> wrote:
>
>> Protect ssh with the following:
>>
>> 1. If using passwords, use long, quality passwords--passwords that are
>> *not* recycled elsewhere.
>> 2. If using keys, protect your private keys *very* carefully.
>> 3. If offering accounts to others, worry that they also follow #1 and #2.
>>
>> ssh is a very secure protocol. If you have good keys/passwords, no
>> script kiddie (or even serious foe) is going to break in with a
>> brute-force attack. Moving your sshd to an alternate port number is a
>> silly distraction.
>>
>>
>> -kb, the Kent who also recommends you keep your system up-to-date.
>>
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>