-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A somewhat effective method, that won't chew up any resources, but could
be discovered is to change your sshd port.  If you use a very high
number, only the most aggressive scans will detect the open port, and
even then they have to figure out that it is for ssh.

But, if you know who your attacker is, there are many ways to discourage
them from such activity.  Email the ISP they are using to touch yours
with.  Most ISP will gladly remind them off Internet etiquette.
Especially universities.

Oh, and really don't confuse l337s with script kiddies.  The fact that
you noticed this happening, means he is brute forcing you with scripts.
 You won't notice l33ts, at least as far as I would name them.
~Joshua

Jordan Curzon wrote:
> DenyHosts has been VERY effective for me and it has no noticeable
> impact on resource usage. It is easy to setup and configure.
> 
> http://denyhosts.sourceforge.net/
> 
> On 1/30/06, Michael Torrie <[EMAIL PROTECTED]> wrote:
> 
>>On Mon, 2006-01-30 at 16:41 -0700, Glen Wagley wrote:
>>
>>>I got sick of Brent Thomson trying to hack into my server. I installed
>>>fail2ban [1] last week and so far it seems to be working well. I notice
>>>that it chews the processor like little kids chew gum (often and
>>>non-stop). Is anyone else using this? If you are using something else to
>>>automagically block ssh attacks, what are you using and why do you like
>>>it?
>>
>>I haven't actually implemented anything yet, but here is one that I was
>>looking at:
>>
>>http://www.csc.liv.ac.uk/~greg/sshdfilter/
>>
>>This only does ssh though.
>>
>>Michael
>>
>>
>>
>>>[1] http://fail2ban.sourceforge.net/
>>>
>>
>>--------------------
>>BYU Unix Users Group
>>http://uug.byu.edu/
>>
>>The opinions expressed in this message are the responsibility of their
>>author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
>>___________________________________________________________________
>>List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
>>
> 
> 
> --------------------
> BYU Unix Users Group 
> http://uug.byu.edu/ 
> 
> The opinions expressed in this message are the responsibility of their
> author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
> ___________________________________________________________________
> List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD3t+6yZ4qqW21pBoRAti/AJ4uNQ2mTcDeVTLw99tgRrL9GZRzRACeIeN3
i7xbMqGioX+/m8PgBTz7f2M=
=Zr1A
-----END PGP SIGNATURE-----

--------------------
BYU Unix Users Group 
http://uug.byu.edu/ 

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG. 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to