1 |
On Wed, 2008-02-27 at 21:24 +0100, Remy Blank wrote: |
2 |
|
3 |
> A simple solution is to run sshd on a |
4 |
> non-standard, high-numbered port, e.g. in the 30'000. Bots only ever try |
5 |
> to connect on port 22. This will *not* improve the protection of your |
6 |
> server, but it will avoid having your logs spammed. |
7 |
|
8 |
+1 |
9 |
|
10 |
I hosed my router, and had to go back to an old one that could only |
11 |
forward port 22 to an internal machine port 22. I got lots of brute |
12 |
force attacks. Well, most of them only tried about 5 passwords each, so |
13 |
not exactly brute force... Anyway, once I upgraded my router again and |
14 |
forwarded port x0000 to port 22, I haven't seen one since. |
15 |
|
16 |
HTH, |
17 |
-- |
18 |
Iain Buchanan <iaindb at netspace dot net dot au> |
19 |
|
20 |
Linux - because software problems should not cost money. |
21 |
|
22 |
-- Shlomi Fish |
23 |
|
24 |
-- |
25 |
gentoo-user@l.g.o mailing list |