|
#11
|
||||
|
||||
|
concerning the ssh-problem.. use authentication with public/private keys and disable simple password authentication..
|
|
#12
|
||||
|
||||
|
Moving SSH to i.e. 8543 will decrese number of 'HaCkErS' attacks (attack from side of child with computer).
To prevent access to SSH after some number of failture logins you can use BFD (Brute Force Detection). |
|
#13
|
|||
|
|||
|
My photoblog was also "commented" on by the hacker.....
Deleting the comment in the database with phpmyadmin fixed the problem. thanx for the info in this tread! good night Hans photo.hansdeloof.be
__________________
=== hans === http://photo.hansdeloof.be === |
|
#14
|
|||
|
|||
|
Use Snort and ACID/Base. Perfect for what you are talking about doing for temp protection and whatching port scanners and alike.
|
|
#15
|
||||
|
||||
|
I use blockhosts 1.0.4 now and that works oke to block brute-ssh-attacks or brute-ftp-attacks.
__________________
Northing.nl |
| Post Reply |
| Thread Tools | |
|
|